From: Heime <heimeborgia@protonmail.com>
To: Yuri Khan <yuri.v.khan@gmail.com>
Cc: Heime via Users list for the GNU Emacs text editor
<help-gnu-emacs@gnu.org>
Subject: Re: Regexp with comment character of buffer
Date: Mon, 12 Aug 2024 19:22:23 +0000 [thread overview]
Message-ID: <j8qNMFgaiDlX9rncq8DHZWxVW10-SeGDqLkOPfd97XPCa_gTX4CV4qTy4KWxNCMhV2K55RLth-6BsJHLgU2aNOwUYeaX6puN1GLkpio5nbc=@protonmail.com> (raw)
In-Reply-To: <GzwpG3HMVbhA4P1X31HuXOFUIEWfmXmna_-PnWlpR4HXM5tF-Zqxvm2SoFUC5hIrwbMpOngqs2dl_541nVr7Vdr8mXmkHRhI-MtR1XZQ8kQ=@protonmail.com>
Sent with Proton Mail secure email.
On Tuesday, August 13th, 2024 at 7:19 AM, Heime <heimeborgia@protonmail.com> wrote:
>
>
>
>
>
> Sent with Proton Mail secure email.
>
>
> On Tuesday, August 13th, 2024 at 7:13 AM, Yuri Khan yuri.v.khan@gmail.com wrote:
>
> > On Tue, 13 Aug 2024 at 00:50, Heime heimeborgia@protonmail.com wrote:
> >
> > > Is the space part of 'comment-start'. It is difficult to say from the code.
> >
> > You do not have to say that from code. You activate a buffer and do an
> > M-: comment-start RET, and look at the result in the echo area. Repeat
> > with a different mode.
> >
> > Alternatively, you read Emacs sources, see that many but not all modes
> > set comment-start with a trailing space.
Users should not be doing that, and figure out additional things are being
added for convenience. It is not a good strategy.
> comment-start should not introduce a trailing space for convenience, but added
> later, so users can start writing the comment after a space.
>
> > > Can I just use `comment-start` without trimming it ?
> >
> > Since you’re using string-to-char which is documented to return only
> > the first character of the input string, it does not matter if you
> > trim the original string beforehand.
prev parent reply other threads:[~2024-08-12 19:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-12 10:08 Regexp with comment character of buffer Heime
2024-08-12 11:03 ` Yuri Khan
2024-08-12 11:41 ` Heime
2024-08-12 12:26 ` Yuri Khan
2024-08-12 12:36 ` Heime
2024-08-12 17:11 ` Yuri Khan
2024-08-12 17:50 ` Heime
2024-08-12 19:13 ` Yuri Khan
2024-08-12 19:19 ` Heime
2024-08-12 19:22 ` Heime [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='j8qNMFgaiDlX9rncq8DHZWxVW10-SeGDqLkOPfd97XPCa_gTX4CV4qTy4KWxNCMhV2K55RLth-6BsJHLgU2aNOwUYeaX6puN1GLkpio5nbc=@protonmail.com' \
--to=heimeborgia@protonmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=yuri.v.khan@gmail.com \
/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.
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).