From: "Drew Adams" <drew.adams@oracle.com>
To: <emacs-devel@gnu.org>
Subject: RE: display.texi: (<line>,<col>) isn't documented.
Date: Thu, 7 Jun 2007 08:30:36 -0700 [thread overview]
Message-ID: <EIENLHALHGIMHGDOLMIMEEDFDCAA.drew.adams@oracle.com> (raw)
In-Reply-To: <ebe43d680706070817w531dbc7bxfcf92d3f4b1f573f@mail.gmail.com>
> > column only - 67x
> > line only - 234y
> > line & column - 67x234y
>
> It's abnormal to put the column first (for example compiler error
> messages), so this would be confusing.
We could certainly decide on either order, but I cannot imagine that 234y67x
is more universal or less "abnormal" than 67x234y.
The main point is that either order would be clear (i.e. would not "be
confusing"), because of the explicit dimension indicators `x' and `y'. The
same is not true of the other suggestions (except for `C' and `L').
What's the connection with compiler error messages? This is interactive
feedback about cursor position in a buffer. In compiler output, you are
primarily (as in first) interested in the line number. That's not the case
here - you might be interested in either or both. Yes, it would be
"abnormal" for compiler messages to list the column number first. I don't
see why that's pertinent here.
next prev parent reply other threads:[~2007-06-07 15:30 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-05 23:19 display.texi: (<line>,<col>) isn't documented Alan Mackenzie
2007-06-06 16:59 ` Richard Stallman
2007-06-06 17:36 ` mode line: 1) indicate region size, if active; 2) highlight column # if > limit Drew Adams
2007-06-06 17:44 ` David House
2007-06-06 18:19 ` Drew Adams
2007-06-06 18:26 ` David House
2007-06-06 18:41 ` chad brown
2007-06-08 7:12 ` Richard Stallman
2007-06-22 23:13 ` Drew Adams
2007-06-23 13:19 ` Richard Stallman
2007-06-23 19:52 ` Juri Linkov
2007-06-24 14:40 ` Richard Stallman
2007-06-06 19:44 ` display.texi: (<line>,<col>) isn't documented David Kastrup
2007-06-06 20:07 ` Stefan Monnier
2007-06-06 20:09 ` Juanma Barranquero
2007-06-06 21:27 ` Juri Linkov
2007-06-07 15:12 ` Drew Adams
2007-06-07 15:17 ` David House
2007-06-07 15:30 ` Drew Adams [this message]
2007-06-07 15:40 ` Lennart Borgman (gmail)
2007-06-07 15:42 ` David House
2007-06-07 15:35 ` Juanma Barranquero
2007-06-07 15:44 ` David House
2007-06-07 15:45 ` Thomas Hühn
2007-06-07 15:49 ` Andreas Schwab
2007-06-07 16:15 ` Dieter Wilhelm
2007-06-07 17:18 ` Drew Adams
2007-06-07 17:28 ` Thomas Hühn
2007-06-07 17:42 ` Juanma Barranquero
2007-06-07 19:39 ` Jay Belanger
2007-06-07 20:17 ` Juri Linkov
2007-06-07 18:13 ` Dieter Wilhelm
2007-06-07 20:26 ` Alan Mackenzie
2007-06-07 21:20 ` Drew Adams
2007-06-07 21:33 ` Davis Herring
2007-06-08 14:24 ` Richard Stallman
2007-06-08 15:09 ` Drew Adams
2007-06-09 20:24 ` Richard Stallman
2007-06-09 20:35 ` Drew Adams
2007-06-09 21:34 ` Juri Linkov
2007-06-10 15:02 ` Drew Adams
2007-06-10 23:24 ` Johan Bockgård
2007-06-11 9:44 ` Richard Stallman
2007-06-11 17:21 ` Drew Adams
2007-06-13 8:07 ` Richard Stallman
2007-06-13 8:07 ` Richard Stallman
2007-06-10 13:18 ` Richard Stallman
2007-06-10 15:15 ` Drew Adams
2007-06-11 3:40 ` Miles Bader
2007-06-11 5:32 ` Drew Adams
2007-06-11 9:44 ` Richard Stallman
2007-06-11 9:50 ` David House
2007-06-11 17:30 ` Drew Adams
2007-06-08 7:11 ` Richard Stallman
2007-06-08 7:26 ` Thien-Thi Nguyen
2007-06-08 8:15 ` Kim F. Storm
2007-06-08 9:42 ` David House
2007-06-09 9:45 ` Richard Stallman
2007-06-08 8:11 ` Kim F. Storm
2007-06-08 8:38 ` Juri Linkov
2007-06-08 20:05 ` Dieter Wilhelm
2007-06-08 8:48 ` Nick Roberts
2007-06-06 21:57 ` Stephen Berman
2007-06-07 5:05 ` Werner LEMBERG
2007-06-10 8:35 ` Daniel Brockman
2007-06-10 14:27 ` Juri Linkov
2007-06-06 23:53 ` Jay Belanger
2007-06-07 0:07 ` David Kastrup
2007-06-07 0:08 ` Nick Roberts
2007-06-08 12:06 ` Alan Mackenzie
2007-06-07 8:23 ` tomas
2007-06-07 17:25 ` Alan Mackenzie
2007-06-08 8:26 ` tomas
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=EIENLHALHGIMHGDOLMIMEEDFDCAA.drew.adams@oracle.com \
--to=drew.adams@oracle.com \
--cc=emacs-devel@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.
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.