unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Emanuel Berg <moasenwood@zoho.eu>
Cc: "'Help-Gnu-Emacs \(help-gnu-emacs@gnu.org\)'" <help-gnu-emacs@gnu.org>
Subject: RE: [External] : messages to *Messages* without appearing in mini-buffer?
Date: Fri, 12 Nov 2021 01:47:42 +0000	[thread overview]
Message-ID: <SJ0PR10MB5488AE0A2569F3AAF431169DF3959@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <87tugi9pvo.fsf@zoho.eu>

[-- Attachment #1: Type: text/plain, Size: 778 bytes --]

> >>> (let ((inhibit-message  t))
> >>>   (message "Msg only to be logged in *Messages*"))
> >>
> >> Doesn't work for me?
> >>
> >> I see it.
> >>
> >> Dont know if message displays it or if it is displayed because
> >> it is returned.
> >
> > What you see is the printed return value of
> > the sexp you asked to evaluate-AND-PRINT.
> > Try `eval-region' on the sexp instead.
> > Or put it in a defun and invoke the function in a way that
> > doesn't also print its return value.
> 
> (progn
>   (message "But then why don't you just do that?")
>   1)

Because you don't need to do that, to prevent
`message' from displaying in the echo area.

Printing a return value from evaluating a sexp
has nothing to do with the question.  See the
Subject line.

[-- Attachment #2: winmail.dat --]
[-- Type: application/ms-tnef, Size: 14166 bytes --]

  reply	other threads:[~2021-11-12  1:47 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-11 14:33 messages to *Messages* without appearing in mini-buffer? Eric S Fraga
2021-11-11 14:45 ` Gregory Heytings
2021-11-11 14:55   ` Eric S Fraga
2021-11-11 17:01 ` [External] : " Drew Adams
2021-11-11 17:07   ` Eric S Fraga
2021-11-12  0:10   ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-11-12  0:16     ` Gregory Heytings
2021-11-12  0:36       ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-11-12  2:08         ` Michael Heerdegen
2021-11-12  3:20           ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-11-12  3:56             ` Michael Heerdegen
2021-11-12  4:02               ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-11-12  4:13                 ` Michael Heerdegen
2021-11-12  4:28                   ` Michael Heerdegen
2021-11-12  5:00                     ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-11-12  5:07                   ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-11-12  5:19                     ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-11-12 21:31                     ` Michael Heerdegen
2021-11-12 21:36                       ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-11-12 17:06                 ` Drew Adams
2021-11-21 11:08                   ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-11-12  0:20     ` Drew Adams
2021-11-12  0:30       ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-11-12  1:47         ` Drew Adams [this message]
2021-11-12  3:10           ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-11-12 17:01             ` Drew Adams

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=SJ0PR10MB5488AE0A2569F3AAF431169DF3959@SJ0PR10MB5488.namprd10.prod.outlook.com \
    --to=drew.adams@oracle.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=moasenwood@zoho.eu \
    /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).