all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: phillip.lord@russet.org.uk (Phillip Lord)
To: Drew Adams <drew.adams@oracle.com>
Cc: help-gnu-emacs@gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: use-package
Date: Thu, 05 May 2016 14:34:59 +0100	[thread overview]
Message-ID: <87shxwzkzg.fsf@russet.org.uk> (raw)
In-Reply-To: <a5a0410b-b798-4809-a5cb-55b1151f99f4@default> (Drew Adams's message of "Wed, 4 May 2016 09:44:24 -0700 (PDT)")

Drew Adams <drew.adams@oracle.com> writes:

>> For example, diminishing minor modes -- I think we have overloaded the
>> functionality of minor modes; many (company say, or eldoc) you either
>> want on or off. Do I really need mode-line space to be taken up telling
>> me that company is one? And is the mode-line the only place we can
>> display this information?
>
> There are of course ways (e.g. packages) to reduce the mode-line
> indications.  But I think it might be good if vanilla Emacs provided
> a simple way for a user to not display particular lighters (mode
> indications in the mode-line).

I don't think this is the right solution. Asking the user to choose
which lighters to hide is just passing the buck.

Currently my mode lighter is

Message pab MML yas Helm Abbrev Fill Narrow

pab == pabbrev is my own abbrev mode, but diminished
MML == is attachement
yas == yasnippet diminished
Helm == Completion
Abbrev == Another abbrev expansion
Fill == auto fill.
Narrow == is narrowing

Of these, pab is global, so why show it? MML is only and always on with
message, so why show it (right click functionality is in the main menu)?
yas is always on, so why show it? Helm is always on. Abbrev, not sure
why it is on. Narrow, actually I don't know what is being hidden in
message -- it's certainly not user functionality.

Only "Fill" tells me anything useful, since I turn this on and off in
the same buffer, and "Message", since knowing the mode is good.

Phil





  reply	other threads:[~2016-05-05 13:34 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-02 17:07 use-package Uwe Brauer
2016-05-02 18:47 ` use-package Kaushal Modi
2016-05-03 10:47   ` use-package Uwe Brauer
2016-05-03 14:01     ` use-package Kaushal Modi
2016-05-03 22:28       ` use-package Stefan Monnier
2016-05-04  3:33         ` use-package Kaushal Modi
2016-05-04 12:09           ` use-package Stefan Monnier
2016-05-04 16:22         ` use-package Phillip Lord
2016-05-04 16:44           ` use-package Drew Adams
2016-05-05 13:34             ` Phillip Lord [this message]
2016-05-05 14:00               ` use-package Drew Adams
2016-05-05 15:56                 ` use-package Kaushal Modi
2016-05-05 16:12                   ` use-package Drew Adams
2016-05-10  9:20                     ` use-package Phillip Lord
2016-05-10  9:18                   ` use-package Phillip Lord
2016-05-11 11:42                     ` use-package Kaushal Modi
2016-05-12 21:04                       ` use-package Phillip Lord
2016-05-13 11:56                         ` use-package Stefan Monnier
2016-05-14 22:27                           ` use-package Phillip Lord
2016-05-15  3:22                             ` use-package Stefan Monnier
2016-05-13 15:38                         ` use-package Drew Adams
2016-05-16 15:16                           ` use-package Phillip Lord
2016-05-16 16:49                             ` use-package Drew Adams
     [not found]                         ` <mailman.2761.1463153947.7477.help-gnu-emacs@gnu.org>
2016-05-14  7:37                           ` use-package Rusi
2016-05-10  9:13                 ` use-package Phillip Lord
2016-05-05  9:51       ` use-package Uwe Brauer
2016-05-05 13:38         ` use-package Phillip Lord
2016-05-03 22:21 ` use-package Stefan Monnier
2016-05-05 10:15   ` use-package Uwe Brauer
2016-05-05 23:41     ` use-package Stefan Monnier

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=87shxwzkzg.fsf@russet.org.uk \
    --to=phillip.lord@russet.org.uk \
    --cc=drew.adams@oracle.com \
    --cc=help-gnu-emacs@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 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.