Re: Newbie: Interactive goto-line ?!

[floyd@barrow.com (Floyd L. Davidson)]

David Kastrup <dak@gnu.org> wrote:
>Jesper Harder <harder@myrealbox.com> writes:
>>
>> I agree.  Which begs the question: Why on earth is it turned _off_
>> by default?
>
>I have it turned off.  I use Emacs mostly for TeX programming, and
>there its competence in analysing complex TeX documents is not
>convincing (complex TeX documents can hardly be tackled by anything
>but TeX, since syntax categories in this macro language change on the
>fly).
>
>I am exposed to large amounts of text all the time.  The contrast on
>screen is already much lower than on paper, I need not lower it more
>artificially.  In a typical TeX macro document, more than half of the
>important text consists of comments.  Making those less readable by
>casting them into some weird color is contraproductive.

This is indeed a significant problem.  I've tried, with no
success, to find a way to change font-lock face colors when
switching between major modes.  That is because what for me is
appropriate for C or Lisp programming is one set, which just
makes TeX too hard to look at, or the other way around.  I can
manage to set up manually invoked reconfigurations of face
properties, but I've not had any luck at all trying to change
them automatically when switching from one buffer to another
where different major modes are being used in the two buffers.

That is something I would really like to have.

>Colored text is also disadvantaging people with reading disabilities.
>Using a full-contrast display at the start for configuring an
>unreadable one is easier than using an unreadable one for configuring
>a full-contrast display.

!!  However, I'm somewhat the opposite, and try to avoid eye
strain by reducing the contrast, or even more, by reducing the
overall brightness of the screen (I can't tolerate a white
background for very long, as an example).  Yet widely varying
levels of contrast between different colored text is just
extremely annoying to me.  So the trick is to find different
color combinations that are about the same level of contrast for
any text that I want to read.  Then I choose low contrast for
text that I want to become invisible yet available to verify
that it does exist (but does not need to be actually read).  And
I want only things that need immediate attention to be either
bright or high contrast.  If I want to force my attention to it
immediately, it can be bright white or bright red, because I
can't stand having either of them on the screen!

>On of the few customizations I use when testing things with XEmacs is
>to turn off its default font lock mode.

Regardless, the idea that next-error eliminates the need for
using goto-line is only true for people doing certain kinds of
editing.  It is great for C programming, but even there it
doesn't solve all problems (and the suggestion that the
compilation buffer is still available is ridiculous compared to
the ease of using M-g for goto-line).

I think the significance of all this is that we all use a
very configurable editor *because* we do so many different things
in so many different ways.  It doesn't bother me a bit that GNU
Emacs uses one binding for M-g and XEmacs uses a different binding,
because in either case it is easy to bind M-g to whatever I want.

I do take offense at someone suggesting that M-g should not be
rebound to goto-line (or whatever).  Bindings aren't sacred at
the user level.  And command usage varies with each user and
with the type of work being done.

--
Floyd L. Davidson           <http://web.newsguy.com/floyd_davidson>
Ukpeagvik (Barrow, Alaska)                         floyd@barrow.com