Gnus development mailing list
 help / color / mirror / Atom feed
From: Bill Wohler <wohler@newt.com>
Cc: mh-e-users@lists.sourceforge.net, ding@gnus.org, emacs-devel@gnu.org
Subject: Re: [ol@i3s.unice.fr: Re: Emacs 20.0.91 pretest available]
Date: Tue, 28 Nov 2006 21:18:08 -0800	[thread overview]
Message-ID: <15629.1164777488@olgas.newt.com> (raw)
In-Reply-To: <E1GpG8I-00085V-P5@fencepost.gnu.org>

Olivier Lecarme <ol@i3s.unice.fr> wrote:

> I'm using [Emacs 22] on a daily basis on all these machines, and did not yet
> encounter any problem. My only remark, for the present, is that in MH-E
> folder mode, the icon showing mail available is so far on the right that
> it cannot be seen in a normal window (if the date and time are shown in
> the mode line). This was not the case in the previous version.

Hi Olivier!

Richard had originally contacted me and I responded to him as follows:

Bill Wohler <wohler@newt.com> wrote:

> This is actually something I've noticed as well. This is not due to a
> change in MH-E--we've only added a logo which added 2 characters. The
> big change is the reorganization of the mode line between Emacs 21 and
> 22: the file location information such as "All L12", which was
> previously on the right, was swapped with the time, load average, and
> mail indicator. Instead of being in the middle, the mail indicator is
> now on the far right and is often cut off, and not only in MH-E buffers.
> 
> To fix this, I'd suggest removing some space around the file location so
> that there is always just two spaces on either side of it. There is
> currently three spaces before it, and up to five spaces after it. The
> first three can certainly be two; I understand that the remaining space
> is there to keep the mode line from flickering as you move around the
> file, but I think the redrawing of the mode line is less of a problem
> than the loss of information.

While removing the extra space will help, upon further reflection, I
have a feeling that we (the MH-E team) will have to clean up the
mode-line some. I'm widening the distribution to get some feedback and
suggestions.

For example, I'm looking at the following mode line:

1:%%  XX  {+outbox/select} 60 msgs (15266-15325)   Bot L60    (MH-Folder Show MC

Note how with a lot of messages, the mode-line real estate is chewed up.

Here's another example:

1:%%  XX  {+mhe-index/foo_and_bar__and_baz} no msgs   All L1     (MH-Folder MC-r

So, long folder names will chew up real estate too.

Here are a couple of ideas:

1. Remove the number of messages in the MH-Folder mode line. In the
   example above, the "60 msgs" text is usually redundant and can be
   largely inferred (if there aren't many holes) from the range of
   messages.

2. Remove the number of messages and the range of messages from the mode
   line (for example, "60 msgs (15266-15325)" above) since you can
   easily get that information by looking at the first message and last
   message in the buffer.

3. Remove the /select from the folder name (which shows that we're only
   looking at a part of a folder--see
   mh-partial-folder-mode-line-annotation). Alternatively, setting
   mh-partial-folder-mode-line-annotation to a single character such as
   `-' might enough to show that you'd only looking at a subset of a
   folder.

4. Use a variant of the Gnus newsgroup abbreviation if the folder name
   is longer than a certain threshold. For example, gmane.emacs.devel is
   g.e.devel. Would we use a similar heuristic?

5. Truncate folder names to 20 characters.

If you're an MH-E user, are any of these ideas repugnant to you? Do any
appeal to you? If you're an Emacs/Gnus developer, can you suggest best
practices for the mode line that our users can evaluate?

Thanks!

-- 
Bill Wohler <wohler@newt.com>  http://www.newt.com/wohler/  GnuPG ID:610BD9AD

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

       reply	other threads:[~2006-11-29  5:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1GpG8I-00085V-P5@fencepost.gnu.org>
2006-11-29  5:18 ` Bill Wohler [this message]
2006-11-29  7:56   ` Olivier Lecarme
2006-11-30  3:20   ` Richard Stallman
2006-11-30  7:05     ` Bill Wohler

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=15629.1164777488@olgas.newt.com \
    --to=wohler@newt.com \
    --cc=ding@gnus.org \
    --cc=emacs-devel@gnu.org \
    --cc=mh-e-users@lists.sourceforge.net \
    /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 NNTP newsgroup(s).