From: Tomas Nordin <tomasn@posteo.net>
To: Jean Louis <bugs@gnu.support>, Bob Newell <bobnewell@bobnewell.net>
Cc: help-gnu-emacs@gnu.org, Tomas Hlavaty <tom@logand.com>
Subject: Re: finding stuff
Date: Sun, 24 Jan 2021 12:09:34 +0100 [thread overview]
Message-ID: <87zh0ya8wh.fsf@posteo.net> (raw)
In-Reply-To: <YA0gMiP7vWO9dWls@protected.rcdrun.com>
Jean Louis <bugs@gnu.support> writes:
> * Bob Newell <bobnewell@bobnewell.net> [2021-01-24 08:34]:
>> If I understand your needs correctly, 'apropos' will give you some of
>> what you want. However it won't search the info files, news, etc.
>>
>> But actually for learning how to do something, web search really is
>> the best option.
>
> For specific stuff the web search provides solutions.
Maybe the stuff actually found typically is specific, but the search on
the web is so general it must be hard to compete with.
It has happened to me a number of times I search the web on some Emacs
question, find links to the Emacs manual wich provide the answer and
only by then understand I would have found it by a direct search in the
manual.
But there must be nothing wrong with this combination of searching the
web and searching Emacs. Sometimes even if something is described in
detail in the manual, it is faster or more convenient to see some
user-written example on the web.
next prev parent reply other threads:[~2021-01-24 11:09 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-24 2:33 finding stuff Tomas Hlavaty
2021-01-24 5:33 ` Bob Newell
2021-01-24 7:22 ` Jean Louis
2021-01-24 11:09 ` Tomas Nordin [this message]
2021-01-24 7:13 ` Jean Louis
2021-01-24 16:26 ` John Yates
2021-01-25 16:31 ` [External] : " Drew Adams
2021-01-25 17:02 ` Eli Zaretskii
2021-01-25 17:37 ` Bob Newell
2021-01-25 19:39 ` John Yates
2021-01-25 20:59 ` Stefan Monnier
2021-01-26 10:33 ` Robert Pluim
2021-01-26 21:09 ` Drew Adams
2021-01-26 1:38 ` moasenwood--- via Users list for the GNU Emacs text editor
2021-01-26 21:06 ` Bob Newell
2021-01-26 5:21 ` Drew Adams
2021-01-26 5:45 ` moasenwood--- via Users list for the GNU Emacs text editor
2021-01-26 21:09 ` Drew Adams
2021-01-26 22:16 ` John Yates
2021-01-26 23:28 ` Drew Adams
2021-01-27 6:29 ` moasenwood--- via Users list for the GNU Emacs text editor
2021-01-26 15:02 ` Eli Zaretskii
2021-01-26 21:17 ` Drew Adams
2021-01-27 6:39 ` moasenwood--- via Users list for the GNU Emacs text editor
2021-01-27 6:43 ` moasenwood--- via Users list for the GNU Emacs text editor
2021-01-27 18:43 ` Drew Adams
2021-01-27 18:59 ` moasenwood--- via Users list for the GNU Emacs text editor
2021-01-27 18:24 ` Drew Adams
2021-01-27 18:34 ` moasenwood--- via Users list for the GNU Emacs text editor
2021-01-26 1:58 ` Robert Thorpe
2021-01-26 14:49 ` John Yates
2021-01-27 11:33 ` doltes doltes
2021-01-24 9:18 ` Jude DaShiell
2021-01-24 10:58 ` Tomas Nordin
2021-02-27 1:10 ` Tomas Hlavaty
2021-02-27 2:57 ` Eduardo Ochs
2021-02-27 8:36 ` Tomas Hlavaty
2021-02-27 17:33 ` Eduardo Ochs
2021-02-27 23:25 ` Tomas Hlavaty
2021-02-27 23:28 ` Tomas Hlavaty
2021-02-28 6:20 ` Robert Thorpe
2021-02-28 7:39 ` Tomas Hlavaty
2021-02-28 7:55 ` Jean Louis
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=87zh0ya8wh.fsf@posteo.net \
--to=tomasn@posteo.net \
--cc=bobnewell@bobnewell.net \
--cc=bugs@gnu.support \
--cc=help-gnu-emacs@gnu.org \
--cc=tom@logand.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.
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).