Repository navigation
Emacs configuration examples. - #4
Merged
Merged
Conversation
Examples of Emacs settings for ensuring compliance with coding guidelines.
C-d is for forward delete character.
Member
|
Thanks for this contribution! One tiny thing to change: Your link to the emacs page on the coding guidelines page (new line 80) is in the PEP8 bullet point. Can you instead move it into the note that currently directs to the PEP8 checker script (old line 83-84)? |
Member
|
@phn - just in case you haven't used pull requests before, if you make commits to your branch they will be added to this pull request automatically (no need to open a new pull request) |
Member
|
Looks good to me - thanks! |
astrofrog
added a commit
that referenced
this pull request
Aug 11, 2011
Emacs configuration examples.
mdboom
added a commit
that referenced
this pull request
Jun 13, 2012
…g-fixes Remove 3 of 4 warnings
adrn
referenced
this pull request
in adrn/astropy
Oct 23, 2012
Add exponential notation to LaTeX representation of quantities
cdeil
pushed a commit
to cdeil/astropy
that referenced
this pull request
Sep 25, 2013
Samp sphinx fixes
taldcroft
pushed a commit
that referenced
this pull request
Oct 2, 2015
Throw a warning for any HDF5 error, including large metadata
eteq
pushed a commit
that referenced
this pull request
Dec 6, 2017
Use frame transformations / simplify redshift
saimn
pushed a commit
that referenced
this pull request
Apr 29, 2019
Use literalinclude to include schemas
adrn
pushed a commit
that referenced
this pull request
Oct 24, 2019
This ensures that mixes of superscripts and normal characters fail.
nstarman
referenced
this pull request
in nstarman/astropy
Aug 31, 2020
Co-authored-by: Adrian Price-Whelan <[email protected]>
jeffjennings
pushed a commit
to jeffjennings/astropy
that referenced
this pull request
Jul 2, 2025
Display install info based on the user's OS by default
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I have added a file docs/development/codeguide_emacs.rst, which lists some settings that can help in ensuring compliance with PEP8. The document codeguide.rst has a link to this document.
Sphinx gives a warning that the above file is not included in any toctree. I wasn't sure where to add this document in the current setup. Perhaps we can have an appendix.rst and add codeguide_emacs.rst and others to it.
Prasanth