From: Stefan Monnier <monnier@iro.umontreal.ca>
To: "Óscar Fuentes" <ofv@wanadoo.es>
Cc: emacs-devel@gnu.org
Subject: Re: Using temporary buffers to display messages
Date: Thu, 29 Mar 2012 10:31:24 -0400 [thread overview]
Message-ID: <jwv1uoba3ch.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87vclogml7.fsf@wanadoo.es> ("Óscar Fuentes"'s message of "Thu, 29 Mar 2012 04:36:20 +0200")
> `sunrise-sunset' contains this code, that displays the text on the
> minibuffer if the frame is wide enough and on a temporary buffer
> otherwise:
> (if (<= (length msg) (frame-width))
> (message "%s" msg)
> (with-output-to-temp-buffer "*temp*"
> (princ (concat date-string "\n" time-string)))
> (message "%s"
> (substitute-command-keys
> (if one-window
> (if pop-up-windows
> "Type \\[delete-other-windows] to remove temp window."
> "Type \\[switch-to-buffer] RET to remove temp window.")
> "Type \\[switch-to-buffer-other-window] RET to restore old \
> contents of temp window."))))
> Is it correct nowadays to use a temporary buffer for displaying
> informative text when it doesn't fit on a single line or is it a vestige
> of the times when the minibuffer lacked autoexpand capabilities?
It's not incorrect. As for whether it's the best choice, it depends.
In general, for messages which are expected to be short (tho more
than a single line), I think `message' is the better choice, unless you
can expect that the user will often want to spend a bit of time looking
at the different parts of the message.
Stefan "whose minibuffer never has more than 1 line"
prev parent reply other threads:[~2012-03-29 14:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-29 2:36 Using temporary buffers to display messages Óscar Fuentes
2012-03-29 14:31 ` Stefan Monnier [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwv1uoba3ch.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=ofv@wanadoo.es \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.