From: Chong Yidong <cyd@stupidchicken.com>
Cc: ihs_4664@yahoo.com, emacs-devel@gnu.org,
Paul Pogonyshev <pogonyshev@gmx.net>
Subject: Re: Longlines and insert
Date: Tue, 15 Nov 2005 21:49:10 -0500 [thread overview]
Message-ID: <87d5l19ujd.fsf@stupidchicken.com> (raw)
In-Reply-To: <87wtj9o59w.fsf@cut.bc.hsia.telus.net> (Ryan Yeske's message of "Tue, 15 Nov 2005 15:33:31 -0800")
> I think (and as far as I understood, Chong Yidong does too) that this is
> a welcoming message for future problems. You patch up a piece of code,
> while there are hundreds other lisp files, many of which insert newlines,
> some of which need to be hard. We probably need something generic. At
> the very least we need a convenience function to create a newline-string
> with the necessary properties already set, so we don't have to go over
> the lines above each time.
>
> Doesn't (newline) insert the right kind of newline based on the value
> of `use-hard-newlines'?
`newline' does. The problem is Lisp code that does (insert "foo\n")
next prev parent reply other threads:[~2005-11-16 2:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <874q6fa1t0.wl%david.wallin@ul.ie>
2005-11-15 2:12 ` Longlines and insert Chong Yidong
2005-11-15 19:00 ` Kevin Rodgers
2005-11-15 20:41 ` Paul Pogonyshev
2005-11-15 22:22 ` Kevin Rodgers
2005-11-15 22:24 ` Kim F. Storm
2005-11-16 3:05 ` Chong Yidong
2005-11-16 10:48 ` Richard M. Stallman
2005-11-15 23:09 ` Stefan Monnier
2005-11-16 2:55 ` Chong Yidong
2005-11-16 4:27 ` Stefan Monnier
2005-11-16 22:01 ` Richard M. Stallman
2005-11-16 22:11 ` Chong Yidong
2005-11-17 19:22 ` Kevin Rodgers
2005-11-17 22:01 ` Paul Pogonyshev
2005-11-17 22:52 ` Kevin Rodgers
2005-11-18 15:28 ` Paul Pogonyshev
2005-11-19 1:55 ` Richard M. Stallman
2005-11-15 23:33 ` Ryan Yeske
2005-11-16 2:49 ` Chong Yidong [this message]
2005-11-16 3:02 ` 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=87d5l19ujd.fsf@stupidchicken.com \
--to=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=ihs_4664@yahoo.com \
--cc=pogonyshev@gmx.net \
/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).