unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Xah <xahlee@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: emacs mode line suggestions
Date: Sun, 16 Nov 2008 15:17:44 -0800 (PST)	[thread overview]
Message-ID: <39353809-6edf-4b7e-aae2-e0dd4d614c61@a26g2000prf.googlegroups.com> (raw)
In-Reply-To: mailman.536.1226871605.26697.help-gnu-emacs@gnu.org

On Nov 16, 1:40 pm, Eli Zaretskii <e...@gnu.org> wrote:
> Please explain how you deduce that the cursor percentage is shown.
> Here's what I see (on MS-Windows, but that's the only GUI Emacs I can
> access where I type this): as long as the first and last line shown by
> the window don't move, I see the same percentage, no matter how I move
> the cursor; but when I scroll the window with "C-u 1 C-v" (which
> scrolls by one line without moving buffer position), the percentage
> starts changing, even though cursor is on the same place in the
> buffer.

Ok, i think i know what you are saying.

I had some misunderstanding in my previous post. Here's what i would
suggest:

according to (info "(emacs)Mode Line"), quote:

«
     -CS:CH-FR  BUF      POS LINE   (MAJOR MINOR)------

...

POS tells you whether there is additional text above the top of the
window, or below the bottom.  If your buffer is small and it is all
visible in the window, POS is `All'.  Otherwise, it is `Top' if you
are
looking at the beginning of the buffer, `Bot' if you are looking at
the
end of the buffer, or `NN%', where NN is the percentage of the buffer
above the top of the window.  With Size Indication mode, you can
display the size of the buffer as well.  *Note Optional Mode Line::.
»

what i am thinking is that code word “All”, “Top”, “Bot”, which are
different than NN%, is less intuitive than if it always use the NN%
format.

i think it's perhaps even better if the percentage is simply the
current line number divided by the total num of lines in buffer.

> > > As for what it should do, I don't see why your preference is better
> > > than the current one.  Popping a menu requires another click to
> > > actually select a buffer, whereas the current behavior does it in one
> > > click.
>
> > typically, a user has several user buffers open, and as far as i guess
> > many programers who use emacs extensively has like hundreds of buffers
> > open. Cycling them one by one is not much useful.
>
> No one in their right mind will cycle buffers.  This feature exists if
> your buffer is one or two away.  Anything more than that, you should
> use the menu-bar's Buffers menu (or select the buffer by its name with
> C-x b).

So, when clicking on the buffer name, showing a menu is more useful
than cycling buffer.

> > For one reason, it by default selectively display only some of the
> > minor modes currently on
>
> Perhaps because some minor modes decided not to announce themselves.
> For example, in the buffer where I type this I have "Fly Abbrev Fill"
> as the list of minor modes that I have turned on.

Yes, so that's confusing.

> > > > • Clicking on the major mode name should pop up a contextual menu to
> > > > let user switch to major major modes.
>
> > > Switching a major mode is a very rare command, so having this at your
> > > fingertips makes no sense, IMO.
>
> > switching between modes is not rarely used. I'd estimate it is used
> > every other hour at least.
>
> Please provide some use-cases to back this up.  FWIW, I almost never
> switch the major mode in the same buffer, unless Emacs didn't switch
> into the right one to begin with, and even then I only do that once in
> a given buffer.

those who use *scratch*, or create new buffer, or create new file...
he may need to switch to the righ lang mode. Sometimes when such
buffer is used as a scratch, programer may have more than one lang
inserted into it, and may switch to different mode for the right
syntax coloring.

  Xah
∑ http://xahlee.org/

  parent reply	other threads:[~2008-11-16 23:17 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.215.1226562978.26697.help-gnu-emacs@gnu.org>
2008-11-14 23:18 ` emacs mode line suggestions Xah
2008-11-15  1:02   ` xahlee
2008-11-15  9:23   ` Eli Zaretskii
     [not found]   ` <mailman.423.1226741023.26697.help-gnu-emacs@gnu.org>
2008-11-16  1:54     ` Xah
2008-11-16 18:12       ` Ian Eure
2008-11-18  9:39         ` Kevin Rodgers
2008-11-18 23:25           ` Xavier Maillard
2008-11-16 21:40       ` Eli Zaretskii
     [not found]       ` <mailman.518.1226859137.26697.help-gnu-emacs@gnu.org>
2008-11-16 18:20         ` Richard Riley
2008-11-16 23:12           ` Ian Eure
2008-11-17  8:37             ` Paul R
2008-11-17 15:45               ` Drew Adams
     [not found]               ` <mailman.604.1226937124.26697.help-gnu-emacs@gnu.org>
2008-11-17 16:11                 ` Richard Riley
2008-11-17 18:53                   ` Drew Adams
2008-11-17 19:10                     ` Richard Riley
2008-11-17 19:57                       ` Drew Adams
2008-11-17 20:53                       ` Eli Zaretskii
     [not found]                       ` <mailman.621.1226951870.26697.help-gnu-emacs@gnu.org>
2008-11-17 21:42                         ` Richard Riley
2008-11-18  0:55                           ` Drew Adams
     [not found]                           ` <mailman.641.1226969742.26697.help-gnu-emacs@gnu.org>
2008-11-18  1:08                             ` Richard Riley
2008-11-18  2:55                               ` Drew Adams
2008-11-17 23:37               ` Alan Mackenzie
2008-11-18  7:52                 ` Paul R
2008-11-18 13:48                   ` Alan Mackenzie
     [not found]           ` <mailman.543.1226877138.26697.help-gnu-emacs@gnu.org>
2008-11-16 23:35             ` Richard Riley
2008-11-16 22:45         ` Xah
     [not found]       ` <mailman.536.1226871605.26697.help-gnu-emacs@gnu.org>
2008-11-16 23:17         ` Xah [this message]
2008-11-17 20:39           ` Eli Zaretskii
2008-11-17 23:46             ` Alan Mackenzie
2008-11-18  0:31               ` Lennart Borgman
2008-11-18  9:32               ` Kevin Rodgers
2008-11-18  9:58                 ` Alan Mackenzie
     [not found]             ` <mailman.633.1226964831.26697.help-gnu-emacs@gnu.org>
2008-11-18  9:46               ` Fabrice Niessen
     [not found]           ` <mailman.623.1226954396.26697.help-gnu-emacs@gnu.org>
2008-11-17 22:09             ` Xah
2008-11-18  2:33               ` B. T. Raven
2008-11-18  3:24                 ` Xah
2008-11-18  4:58                   ` B. T. Raven
2008-11-18  6:54                     ` Richard Riley
2008-11-18  4:11               ` Eli Zaretskii

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=39353809-6edf-4b7e-aae2-e0dd4d614c61@a26g2000prf.googlegroups.com \
    --to=xahlee@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    /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).