From: Adam Funk <a24061@yahoo.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Configuring fill-paragraph not to mash the subversion delimiter?
Date: Wed, 21 Mar 2007 13:34:44 +0000 [thread overview]
Message-ID: <kso7d4-jje.ln1@news.ducksburg.com> (raw)
In-Reply-To: mailman.1142.1174348863.7795.help-gnu-emacs@gnu.org
On 2007-03-19, Matthew Flaschen wrote:
> Okay, then just add this to .emacs. It's necessary to set both start
> and separate (separate alone doesn't work):
It's simple and it works.
Thanks!
next prev parent reply other threads:[~2007-03-21 13:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-16 21:21 Configuring fill-paragraph not to mash the subversion delimiter? Adam Funk
2007-03-16 21:49 ` David Hansen
2007-03-16 23:50 ` Matthew Flaschen
[not found] ` <mailman.1038.1174089116.7795.help-gnu-emacs@gnu.org>
2007-03-19 3:52 ` Stefan Monnier
2007-03-19 17:10 ` Adam Funk
2007-03-19 23:59 ` Matthew Flaschen
[not found] ` <mailman.1142.1174348863.7795.help-gnu-emacs@gnu.org>
2007-03-21 13:34 ` Adam Funk [this message]
2007-03-20 19:48 ` Petter Gustad
2007-04-06 19:40 ` Sam Peterson
2007-04-06 19:56 ` Adam Funk
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=kso7d4-jje.ln1@news.ducksburg.com \
--to=a24061@yahoo.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.
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).