From: Tim Cross <theophilusx@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: extra space at the end of lines in source
Date: Wed, 23 Jun 2021 09:56:39 +1000 [thread overview]
Message-ID: <87im25l9m8.fsf@gmail.com> (raw)
In-Reply-To: <2681710.1624389697@apollo2.minshall.org>
Greg Minshall <minshall@umich.edu> writes:
> hi, Sebastien,
>
> thanks for the reply. i remember that thread, but obviously i wasn't
> paying enough attention.
>
>> The downside is that, unless ~org-src--preserve-indentation~ is `t`,
>> when editing a src block, every empty line will be indented with
>> spaces (according to ~org-edit-src-content-indentation~ + the
>> indentation of the #+begin_src line). I think this is reasonable, but
>> perhaps some might disagree.
>
> indeed. i disagree. it's long-term emacs behavior to eliminate spaces
> at the end of lines, at least in programming modes. i don't know what
> would be involved to keep the fix for the original problem (which i was
> also seeing), without adding these extra spaces. but, i suspect it
> would be worth it, if feasible.
>
I'm not sure that is correct. Elimination of spaces at the end of lines
has always been something you could enable (either directly as a setting
in the mode, which might be enabled by default, or via a package like
whitespace.el. I think it would be going against Emacs philosophy to
have a mode automatically remove end of line spaces - this should be
something the user controls.
Of course, the converse is also true. It would be a mistake to have an
Emacs mode add additional whitespace at the end of lines which is not
requested by the user as well. This could also cause issues/conflicts
with packages like whitespace.el or diffs and VCS etc. It may also make
source blocks 'ugly' if you have your Emacs configured to show
additional whitespace at eol.
--
Tim Cross
prev parent reply other threads:[~2021-06-23 0:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-22 11:35 extra space at the end of lines in source Greg Minshall
2021-06-22 13:45 ` Sébastien Miquel
2021-06-22 19:21 ` Greg Minshall
2021-06-22 21:00 ` Sébastien Miquel
2021-06-23 4:08 ` Greg Minshall
2021-06-23 6:08 ` Tim Cross
2021-06-23 17:29 ` [PATCH] " Sébastien Miquel
2021-06-24 8:55 ` Greg Minshall
2021-06-26 8:37 ` Sébastien Miquel
2021-06-26 15:53 ` Greg Minshall
2021-07-10 14:27 ` Greg Minshall
2021-09-26 5:48 ` Bastien
2021-09-26 13:40 ` Greg Minshall
2021-06-22 23:56 ` Tim Cross [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87im25l9m8.fsf@gmail.com \
--to=theophilusx@gmail.com \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).