From: michael@cadilhac.name (Michaël Cadilhac)
Cc: emacs-devel@gnu.org,
Roland Winkler <Roland.Winkler@physik.uni-erlangen.de>
Subject: Re: fortran-fill-paragraph fails
Date: Fri, 29 Dec 2006 23:43:56 +0100 [thread overview]
Message-ID: <87wt4a726r.fsf@lrde.org> (raw)
In-Reply-To: <jwvmz56xvhy.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Fri\, 29 Dec 2006 16\:06\:57 -0500")
[-- Attachment #1.1: Type: text/plain, Size: 1455 bytes --]
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>>> > (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.
... but it would have needed some thinking to get rid of the
« probably » ;-)
I've installed a comment for that. Thanks for your help Stefan!
--
| Michaël `Micha' Cadilhac | Le second degré, |
| Epita/LRDE Promo 2007 | c'est un peu |
| http://michael.cadilhac.name | le verlan sémantique. |
`--JID: michael.cadilhac@gmail.com--' - --'
[-- Attachment #1.2: Type: application/pgp-signature, Size: 188 bytes --]
[-- Attachment #2: Type: text/plain, Size: 142 bytes --]
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
next prev parent reply other threads:[~2006-12-29 22:43 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
2006-12-29 22:43 ` Michaël Cadilhac [this message]
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
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=87wt4a726r.fsf@lrde.org \
--to=michael@cadilhac.name \
--cc=Roland.Winkler@physik.uni-erlangen.de \
--cc=emacs-devel@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 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).