[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Suggestion: Mapping of M-g should be goto-line

From: Jari Aalto
Subject: Re: Suggestion: Mapping of M-g should be goto-line
Date: Thu, 25 Mar 2004 16:16:50 +0200
User-agent: Gnus/5.110002 (No Gnus v0.2) Emacs/21.3 (windows-nt) (i386-msvc-nt5.0.2195)

* Thu 2004-03-25 Danilo Segan <dsegan <AT> gmx.net> mail.default.spool
| Exactly, and it would be even better if it was bound to next-error ...


And your argument to help handling PHP and other web programming
languages errors - which print error line numbers in web page - was

next-error is useless in those an in many other cases with shell
tools, other programs, other utilities spit out line numbers.

M-g is it, goto-line it it.

Using next-line is not the solution. It some weird way of seeing it
"all done Emacs way". Th reality is not  "all Emacs way", although
we might want it.

| ... there's such a need for goto-line only
| because other Emacs features which are the right way are not exposed
| enough: so, we need to expose them instead, not to expose goto-line.

Wrong assumption. You assume that Emacs has all the answers. It hasn't
User got a problem. And he wants Emacs to answer it. next-error won't
do it, but goto-line will
Imagine those web programming error lines in Web pages. Imagine lint
tools, commercial ones, free ones, lines of obscure error message
lines with line numbers. Imagine legacy of other sysadm tools; home
grown and others. Picture it. It's not "all Emacs" or even "educate
users to use Emacs better".

Emacs will never be able to support all those, every variation, every
new tool, every user script. But M-g, goto-line would be there. Ah,
how relaxing that would be.

Swatch @time   http://www.mir.com.my/iTime/itime.htm
Use Licenses!  http://www.linuxjournal.com/article.php?sid=6225
Which Licence? http://www.linuxjournal.com/article.php?sid=4825
OSI Licences   http://www.opensource.org/licenses/

reply via email to

[Prev in Thread] Current Thread [Next in Thread]