unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Emanuel Berg via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: [External] : messages to *Messages* without appearing in mini-buffer?
Date: Fri, 12 Nov 2021 06:19:28 +0100	[thread overview]
Message-ID: <87sfw26jdr.fsf@zoho.eu> (raw)
In-Reply-To: 8735o27yhx.fsf@zoho.eu

> Two are extra keywords, e.g.
>   https://dataswamp.org/~incal/emacs-init/buffer-menu.el
>   - actually I don't know if they are necessary there ... to
>   be global/dynamic/special, I mean?

This cannot be a closure, first the byte-compiler says the
variable it is unused, then its value is void. Not sure
why but it looks involved so probably doesn't work then ...

> One is a map,
>   https://dataswamp.org/~incal/emacs-init/caps-back.el
>   - necessary?

Maps were always done globally with `defvar' what I saw and
I don't know have an idea to do it otherwise ...

> And three are here
>   https://dataswamp.org/~incal/emacs-init/mode-line.el
>   - are they necessary?

Hm ... these three, I wonder what they are?

-- 
underground experts united
https://dataswamp.org/~incal




  reply	other threads:[~2021-11-12  5:19 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 [this message]
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
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=87sfw26jdr.fsf@zoho.eu \
    --to=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).