unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
Subject: RE: what-cursor-position - why not list the line # as well?
Date: Sun, 2 Apr 2006 11:51:05 -0700	[thread overview]
Message-ID: <DNEMKBNJBGPAOPIJOOICOEFODEAA.drew.adams@oracle.com> (raw)
In-Reply-To: <uodzj98wz.fsf@gnu.org>

    > I use both the column and line numbers in the mode line, but
    > I would still find it handy to have both in `C-x =' also.

    *Shrug* If you need that information frequently, you could write a
    simple function that puts it into the kill ring, and bind it to some
    key.

Why "*Shrug*"? Are you upset? I can of course write lots of functions, but
this is something I proposed adding to an existing Emacs command.  The
question is, why not?

The only reason you gave was that that info is already (by default) in the
mode line. That's a fair argument, but I replied: 1) That default behavior
does not mean that it is in the mode line for everyone all of the time. 2)
You cannot copy+paste mode-line info (AFAIK).

Instead of responding to either a) my reasons for making this change or b)
my reasons why your argument against it is insufficient, you tell me that I
can always code the functionality myself, for my own use. Do you think that
reply helps advance the discussion? Can we discuss the pros and cons of the
proposal?

Why such teeth-pulling over a simple (probably trivial) proposal? If you
don't think it's a good idea, please provide some arguments to further the
discussion.

  reply	other threads:[~2006-04-02 18:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-02  1:02 what-cursor-position - why not list the line # as well? Drew Adams
2006-04-02  3:27 ` Eli Zaretskii
2006-04-02 15:05   ` Drew Adams
2006-04-02 17:36     ` Eli Zaretskii
2006-04-02 18:51       ` Drew Adams [this message]
2006-04-02 23:17         ` Stephen Berman
2006-04-03  3:39         ` Eli Zaretskii
2006-04-03  9:51         ` Ehud Karni

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=DNEMKBNJBGPAOPIJOOICOEFODEAA.drew.adams@oracle.com \
    --to=drew.adams@oracle.com \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).