From: Paul Eggert <eggert@cs.ucla.edu>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] master 1a6f595: * src/minibuf.c (read_minibuf): Add a FIXME comment.
Date: Tue, 24 Apr 2018 21:09:50 -0700 [thread overview]
Message-ID: <a3b89f79-d7ef-7668-436b-bf2b45177153@cs.ucla.edu> (raw)
In-Reply-To: <jwvr2n4xe29.fsf-monnier+emacsdiffs@gnu.org>
Stefan Monnier wrote:
> My guess is that it's because the miniwindow is mostly single-line, so
> "prints" usually work better with \n than with LF. I expect that while
> there might not be any prin1/print in sight nowadays that probably
> hasn't always been the case.
I went back to the earliest (circa 1991) minibuf.c in our repository and
couldn't see a print1/print there either.
Perhaps this dates back to an earlier time when the minibuffer (or at least the
minibuffer prompt) couldn't be multiline, so Emacs wanted to output "\n" rather
than an actual newline when prompting or when echoing data.
Anyway, I doubt whether the code is needed now, as multiline prompts and data
work just fine now in the minibuffer.
I filed a bug report for this (Bug#31251) to give others a chance to comment.
next prev parent reply other threads:[~2018-04-25 4:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180424225022.24335.78516@vcs0.savannah.gnu.org>
[not found] ` <20180424225023.4A3C620836@vcs0.savannah.gnu.org>
2018-04-25 1:39 ` [Emacs-diffs] master 1a6f595: * src/minibuf.c (read_minibuf): Add a FIXME comment Stefan Monnier
2018-04-25 4:09 ` Paul Eggert [this message]
2018-04-25 11:59 ` Stefan Monnier
2018-04-25 19:30 ` Paul Eggert
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=a3b89f79-d7ef-7668-436b-bf2b45177153@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).