From: Yuri Khan <yuri.v.khan@gmail.com>
To: Heime <heimeborgia@protonmail.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: Tue, 13 Aug 2024 00:11:59 +0700 [thread overview]
Message-ID: <CAP_d_8Wx9tw+jTjpKLJGch5EhmHPxjCD6EtVKqSc4GuSochEvQ@mail.gmail.com> (raw)
In-Reply-To: <lkrNeh0rntW2CmKXWEbdGejhdfP_GM0hTTjGh4a0KR9A07vz7FvhFXazVP2SDG8SQyw6-XKub0zwzXhSgNflw12Dmx_6Xp5BsJdthr3rCRM=@protonmail.com>
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.
# 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?
next prev parent reply other threads:[~2024-08-12 17:11 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAP_d_8Wx9tw+jTjpKLJGch5EhmHPxjCD6EtVKqSc4GuSochEvQ@mail.gmail.com \
--to=yuri.v.khan@gmail.com \
--cc=heimeborgia@protonmail.com \
--cc=help-gnu-emacs@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.