From: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: "Michaël Cadilhac" <michael@cadilhac.name>, emacs-devel@gnu.org
Subject: Re: fortran-fill-paragraph fails
Date: Fri, 29 Dec 2006 16:06:57 -0500 [thread overview]
Message-ID: <jwvmz56xvhy.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <17810.43383.385509.776556@tfkp07.physik.uni-erlangen.de> (Roland Winkler's message of "Wed\, 27 Dec 2006 18\:12\:23 +0100")
>> > (commark
>> > (comment-string-strip (buffer-substring comstart comin) nil t))
>> > (comment-re
>> > ! (if (string-match comment-start-skip (concat "\0" commark "a"))
>> > (concat "[ \t]*" (regexp-quote commark)
>> > ;; Make sure we only match comments that use
>> > ;; the exact same comment marker.
>>
>> Please add a clear comment explaining the reason for this "\0".
> I must admit that this patch goes much beyond my knowledge of elisp
> hacking. Also, I cannot find anything in the elisp manual explaining
> the meaning of "\0" in this context. If there is a general idea for
> this, I'd much appreciate if it was documented in the elisp manual,
> too. (Or did I look at the wrong spot?)
There's nothing specific to elisp there, and the \0 is just some
arbitrary char: a space would have probably worked just as well.
Stefan
next prev parent reply other threads:[~2006-12-29 21:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m3r6uq778w.fsf@tfkp07.physik.uni-erlangen.de>
2006-12-24 0:15 ` fortran-fill-paragraph fails Michaël Cadilhac
2006-12-24 1:35 ` Roland Winkler
2006-12-24 20:26 ` Michaël Cadilhac
2006-12-25 23:00 ` Stefan Monnier
2006-12-27 17:12 ` Roland Winkler
2006-12-29 21:06 ` Stefan Monnier [this message]
2006-12-29 22:43 ` Michaël Cadilhac
2006-12-30 6:24 ` Richard Stallman
2006-12-30 12:56 ` Michaël Cadilhac
2006-12-31 1:45 ` Richard Stallman
2007-01-02 23:22 ` Stefan Monnier
2007-01-03 21:11 ` Richard Stallman
2007-01-07 20:12 ` Stefan Monnier
2006-12-30 16:04 ` Roland Winkler
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=jwvmz56xvhy.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=michael@cadilhac.name \
/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.