From: Chong Yidong <cyd@stupidchicken.com>
Cc: emacs-devel@gnu.org
Subject: Re: longlines.el fix?
Date: Wed, 23 Nov 2005 12:03:43 -0500 [thread overview]
Message-ID: <87hda3uwi8.fsf@stupidchicken.com> (raw)
In-Reply-To: <8564qjwd8u.fsf@lola.goethe.zz> (David Kastrup's message of "Wed, 23 Nov 2005 17:16:49 +0100")
David Kastrup <dak@gnu.org> writes:
> I just noticed that a suggestion of mine for preserving markers when
> inserting has made it into longlines.el.
>
> In my private copy, I also have the following fix in. Since I rarely
> use longlines.el, it has seen only cursory testing. Does anybody see
> a particular problem with it? If not, maybe we should check it in so
> that it gets some testing.
Looks OK to me. Please check it in.
next prev parent reply other threads:[~2005-11-23 17:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-23 16:16 longlines.el fix? David Kastrup
2005-11-23 17:03 ` Chong Yidong [this message]
2005-11-25 11:11 ` David Kastrup
2005-11-25 16:36 ` Chong Yidong
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=87hda3uwi8.fsf@stupidchicken.com \
--to=cyd@stupidchicken.com \
--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).