all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: despen@verizon.net
To: help-gnu-emacs@gnu.org
Subject: Re: Rapidly navigating buffers using search
Date: Thu, 08 Jul 2010 16:42:15 -0400	[thread overview]
Message-ID: <icvd8pg0yg.fsf@verizon.net> (raw)
In-Reply-To: 87mxu22rbc.fsf@lola.goethe.zz

David Kastrup <dak@gnu.org> writes:

> despen@verizon.net writes:
>
>> Xah Lee <xahlee@gmail.com> writes:
>>
>>> On Jul 7, 3:25 am, Jonathan Groll <li...@groll.co.za> wrote:
>>>>
>>>> Thanks, this is something that I didn't realised until now, and have
>>>> been using emacs for a couple of years... and it is right there in the
>>>> manual under "basics of incremental search" too.
>>>
>>> same here. I started to use emacs daily since 1998, and i didn't
>>> realize that Enter will exit the search and leave the cursor at the
>>> current location untill 2007 or so. I've always just used left/right
>>> arrow. (and a year or two later, i also found out that it is right in
>>> the manual. These happened only when i started to get more involved
>>> in writing a emacs tutorial)
>>>
>>> this situation of us using emacs for 5 or 10 years and often found
>>> something basics we don't know about. I think that means there's
>>> something wrong with the manual.
>>
>> There's nothing wrong with the manual.
>> That makes no sense, you just said the information is in the manual.
>
> I think the point was that the manual was not deficient concerning the
> information it provides, but in not making Xah Lee want to read it.

Well, he should say what he means.

:)

> In a way, it is a losing battle.

Many people will get to a level of proficiency and stop being curious.
I don't see a big problem, if they don't want to be power users,
so be it.
I think it's usually the same people that say they don't have
enough time to learn new things.

There are so many ways to access the "excellent manual" that it's
almost ridiculous.

One can type "^s ^h m" and get a whole lot of good info on isearch.
Some people will realize that they've got a whole screen full of
information and they should periodically go back and read it again
because the whole thing is not going to sink in at once.


  parent reply	other threads:[~2010-07-08 20:42 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-07  6:43 Rapidly navigating buffers using search Jonathan Groll
2010-07-07  6:52 ` Aidan Gauland
2010-07-07  6:54 ` Thierry Volpiatto
2010-07-07  7:40 ` Qiang Guo
2010-07-07  8:01   ` Jonathan Groll
2010-07-07  8:45     ` Andrea Crotti
2010-07-07  9:33       ` Deniz Dogan
2010-07-07 10:25         ` Jonathan Groll
     [not found]         ` <mailman.11.1278498387.2272.help-gnu-emacs@gnu.org>
     [not found]           ` <9dc07ed9-f6f1-4ac5-949a-5b97368cc32a@n19g2000prf.googlegroups.com>
2010-07-08  2:28             ` despen
     [not found]               ` <87mxu22rbc.fsf@lola.goethe.zz>
2010-07-08 17:59                 ` bolega
2010-07-08 22:11                   ` WYSIWYG and usability (was: " Peter Flynn
2010-07-08 20:42                 ` despen [this message]
2010-07-09 21:18                 ` Fixing antediluvianisms in Emacs' UI Ilya Zakharevich
2010-07-10 14:22                   ` Pascal J. Bourguignon
2010-07-09 21:39                 ` Rapidly navigating buffers using search Ilya Zakharevich
2010-07-10 18:13                 ` Xah Lee
2010-07-10 23:25                   ` B. T. Raven
2010-07-11  4:47                     ` Xah Lee
2010-07-11 13:31                       ` B. T. Raven
2010-07-11 16:13                         ` David Kastrup
2010-07-11 21:58                           ` B. T. Raven
     [not found]                         ` <873cd6b9-8a85-478f-9943-c3ce09eb62c6@n8g2000prh.googlegroups.com>
2010-07-11 21:50                           ` B. T. Raven
2010-07-10 21:01             ` Uday S Reddy
2010-07-07 10:54 ` Aidan Gauland
     [not found] <mailman.0.1278485069.2272.help-gnu-emacs@gnu.org>
2010-07-07  8:43 ` Stefan Kamphausen

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=icvd8pg0yg.fsf@verizon.net \
    --to=despen@verizon.net \
    --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.
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.