From: Stefan Kangas <stefankangas@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 60034@debbugs.gnu.org, Heime <heimeborgia@protonmail.com>,
Stefan Monnier <monnier@gnu.org>
Subject: bug#60034: comment character for org and python includes a space
Date: Mon, 11 Sep 2023 01:24:04 -0700 [thread overview]
Message-ID: <CADwFkmn9NJv3_6wW+JK5MhDbBf3a1k+pmQr2fMDgiROxq4FuUg@mail.gmail.com> (raw)
In-Reply-To: <jwvedj577lr.fsf-monnier+emacs@gnu.org>
tags 60034 + notabug wontfix
close 60034
thanks
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>>>> > How is it that the comment character for org and python include a
>>>> > space "# ", when for all other languages it is only a single
>>>> > character?
>
> FWIW, both options are valid and they lead to different results
> when you do `M-;` (as well as as when `-comment-add` is 0).
>
> E.g. ELisp uses ";" rather than "; " so that you can do `M-; ; hello` to
> add a comment of the form `;; hello` at the end of the current line.
>
> In modes where using repetitions of the comment char is unusual
> (typically because indentation rules don't pay attention to the number
> of consecutive comment chars), it's more common to add a space at the
> end of `comment-start`.
Thanks, so I don't think there's anything to fix here. If someone needs
the space-free version, they can use something like:
(string-remove-suffix " " comment-start)
So I'm closing this as a wontfix. Sorry.
prev parent reply other threads:[~2023-09-11 8:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-13 15:27 bug#60034: comment character for org and python includes a space Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-13 18:36 ` Stefan Kangas
2022-12-14 2:35 ` Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-10 18:47 ` Stefan Kangas
2023-09-11 2:46 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-11 8:24 ` Stefan Kangas [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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CADwFkmn9NJv3_6wW+JK5MhDbBf3a1k+pmQr2fMDgiROxq4FuUg@mail.gmail.com \
--to=stefankangas@gmail.com \
--cc=60034@debbugs.gnu.org \
--cc=heimeborgia@protonmail.com \
--cc=monnier@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.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).