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 17:50:52 +0000 [thread overview]
Message-ID: <IR3gD9-I3psm0dy8n2rByXP37ngipUZ4i3xvzY4pesbkBdcA5NtBWYCo76P7QfuX0yz-aj6UZgqR6tn8pSk-C308M4vQ33Vf9RgvzzZfOB4=@protonmail.com> (raw)
In-Reply-To: <CAP_d_8Wx9tw+jTjpKLJGch5EhmHPxjCD6EtVKqSc4GuSochEvQ@mail.gmail.com>
On Tuesday, August 13th, 2024 at 5:11 AM, Yuri Khan <yuri.v.khan@gmail.com> wrote:
> On Mon, 12 Aug 2024 at 19:36, Heime heimeborgia@protonmail.com wrote:
>
> > > > (let* ((comment-char (regexp-quote (string-trim comment-start)))
> > > > (three-comment-chars (make-string 3 (string-to-char comment-char)))
>
> > Is a string-trim required for comment-start ?
>
>
> Required for comment-start? No. What does the docstring for
> comment-start tell you?
>
> String to insert to start a new comment, or[…]
>
> The space is there so that when the string is inserted, the user will
> be able to start typing the comment text and it will be separated from
> the delimiter.
Is the space part of 'comment-start'. It is difficult to say from the code.
Can I just use `comment-start` without trimming it ?
> # comment in shell or Python
> ; comment in Elisp
> // comment in C++
> /* comment in C */
> <!-- comment in HTML -->
>
>
>
> Required for your use of comment-start? Maybe.
>
> Anyway, what’s your plan for modes whose comment-start is longer than
> a single character after trimming the space?
Currently I support modes with single character comments.
next prev parent reply other threads:[~2024-08-12 17:50 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 [this message]
2024-08-12 19:13 ` Yuri Khan
2024-08-12 19:19 ` Heime
2024-08-12 19:22 ` Heime
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='IR3gD9-I3psm0dy8n2rByXP37ngipUZ4i3xvzY4pesbkBdcA5NtBWYCo76P7QfuX0yz-aj6UZgqR6tn8pSk-C308M4vQ33Vf9RgvzzZfOB4=@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).