From: daniela-spit@gmx.it
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Removing line and column number settings from some buffers
Date: Fri, 4 Dec 2020 00:36:14 +0100 [thread overview]
Message-ID: <trinity-1be9f0a2-1071-484e-addc-3fb830408f89-1607038574418@3c-app-mailcom-bs11> (raw)
In-Reply-To: <87tut2a2xg.fsf@web.de>
> Sent: Friday, December 04, 2020 at 12:24 AM
> From: "Michael Heerdegen" <michael_heerdegen@web.de>
> To: help-gnu-emacs@gnu.org
> Subject: Re: Removing line and column number settings from some buffers
>
> daniela-spit@gmx.it writes:
>
> > Got it, thank you.
> >
> > Am also trying to see what is what. When I removed some of the options,
> > the mode line still remained the same.
>
> Some elements only display something under certain circumstances.
>
> Another thing is that mode-line-format "Automatically becomes
> buffer-local when set." If you want to see an effect nearly everywhere,
> you must change the default value of the symbol. Some modes don't use
> the default mode-line display but implement an own one so these would
> not be affected (when changing the default).
>
> Or modify the variables that represent parts of the mode-line and have
> their own variable. This is often the better alternative for global
> mode-line config, in my experience.
Yes, modifying variables representing parts of mode-line helped
me get somewhere.
> Regards,
>
> Michael.
>
>
>
prev parent reply other threads:[~2020-12-03 23:36 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-02 15:34 Removing line and column number settings from some buffers daniela-spit
2020-12-02 21:18 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-02 23:21 ` daniela-spit
2020-12-02 23:28 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-02 23:32 ` daniela-spit
2020-12-02 23:56 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-02 23:57 ` daniela-spit
2020-12-03 0:04 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-03 22:14 ` Michael Heerdegen
2020-12-03 22:19 ` daniela-spit
2020-12-03 22:22 ` Jean Louis
2020-12-03 22:33 ` daniela-spit
2020-12-03 22:52 ` Jean Louis
2020-12-03 23:09 ` daniela-spit
2020-12-04 0:38 ` Christopher Dimech
2020-12-04 1:16 ` Michael Heerdegen
2020-12-04 1:33 ` Christopher Dimech
2020-12-04 2:10 ` daniela-spit
2020-12-04 2:42 ` Christopher Dimech
2020-12-04 6:10 ` Jean Louis
2020-12-04 6:31 ` Christopher Dimech
2020-12-04 8:40 ` Eli Zaretskii
2020-12-05 5:13 ` Christopher Dimech
2020-12-05 15:41 ` Drew Adams
2020-12-05 17:58 ` Jean Louis
2020-12-05 18:16 ` Drew Adams
2020-12-05 18:57 ` Jean Louis
2020-12-04 2:46 ` Michael Heerdegen
2020-12-04 3:12 ` Christopher Dimech
2020-12-04 4:16 ` daniela-spit
2020-12-04 4:36 ` daniela-spit
2020-12-04 5:58 ` daniela-spit
2020-12-04 7:19 ` Jean Louis
2020-12-05 4:42 ` daniela-spit
2020-12-05 21:32 ` Michael Heerdegen
2020-12-05 21:35 ` Michael Heerdegen
2020-12-05 22:54 ` daniela-spit
2020-12-05 22:57 ` Drew Adams
2020-12-05 23:05 ` daniela-spit
2020-12-05 23:37 ` Drew Adams
2020-12-05 23:53 ` daniela-spit
2020-12-04 7:40 ` Jean Louis
2020-12-04 6:07 ` Jean Louis
2020-12-03 23:24 ` Michael Heerdegen
2020-12-03 23:36 ` daniela-spit [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
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=trinity-1be9f0a2-1071-484e-addc-3fb830408f89-1607038574418@3c-app-mailcom-bs11 \
--to=daniela-spit@gmx.it \
--cc=help-gnu-emacs@gnu.org \
--cc=michael_heerdegen@web.de \
/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).