From: Juri Linkov <juri@jurta.org>
Cc: lennart.borgman.073@student.lu.se, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Todays exercise of sanity (or does "see" really match "not"?)
Date: Thu, 24 Mar 2005 02:21:52 +0200 [thread overview]
Message-ID: <87u0n2hqrr.fsf@jurta.org> (raw)
In-Reply-To: <200503232116.j2NLGfp07884@raven.dms.auburn.edu> (Luc Teirlinck's message of "Wed, 23 Mar 2005 15:16:41 -0600 (CST)")
> `*Note' _is_ a part of the text. It occurs in the output produced by
> `makeinfo --plaintext', which, since it is entirely plain text, does
> not have _any_ special markers. Anyway, rather than to argue over
> terminology, the important thing is: the user sees it, search has to
> find it. Note that both `s' and `C-s' in standalone Info correctly
> match `*Note'. If `not' would not match `*Note' in Emacs Info with
> Info-hide-note-references set to t, then this would be very confusing.
====
Did you mean "Info-hide-note-references set to nil"?
> It would make people start to doubt the reliability of search in
> Emacs. (What _other_ stuff does search in Emacs ignore?) It would be
> an outright bug.
Isearch ignores text with `invisible' text properties and hidden
overlays according to `buffer-invisibility-spec'.
Info-search ignores Info files headers, header lines and Tag Table
nodes.
> Sorry for misspelling your name once more in my previous reply.
> I do not know why I keep doing this.
I guess it's because you manually type a citation line every time
you write a response. To insert it automatically you can use message.el
and set `message-citation-line-function' to `message-insert-citation-line'.
--
Juri Linkov
http://www.jurta.org/emacs/
next prev parent reply other threads:[~2005-03-24 0:21 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-21 13:20 Todays exercise of sanity (or does "see" really match "not"?) Lennart Borgman
2005-03-21 13:49 ` Luc Teirlinck
2005-03-21 14:00 ` Lennart Borgman
2005-03-21 19:27 ` Juri Linkov
2005-03-21 20:18 ` David Kastrup
2005-03-22 13:57 ` Richard Stallman
2005-03-22 14:46 ` David Kastrup
2005-03-22 17:29 ` Juri Linkov
2005-03-22 22:22 ` David Kastrup
2005-03-23 6:21 ` Richard Stallman
2005-03-23 13:08 ` Juri Linkov
2005-03-23 14:19 ` Luc Teirlinck
2005-03-23 15:19 ` Juri Linkov
2005-03-23 17:03 ` Luc Teirlinck
2005-03-23 20:21 ` Juri Linkov
2005-03-23 20:33 ` Stefan Monnier
2005-03-23 21:16 ` Luc Teirlinck
2005-03-23 21:42 ` Luc Teirlinck
2005-03-23 22:54 ` Kim F. Storm
2005-03-24 1:18 ` Luc Teirlinck
2005-03-25 6:42 ` Richard Stallman
2005-03-23 21:44 ` Drew Adams
2005-03-24 0:21 ` Juri Linkov [this message]
2005-03-24 1:12 ` Luc Teirlinck
2005-03-25 6:41 ` Richard Stallman
2005-03-23 21:30 ` Luc Teirlinck
2005-03-24 5:18 ` Richard Stallman
2005-03-23 20:26 ` Richard Stallman
2005-03-24 0:19 ` Juri Linkov
2005-03-25 6:42 ` Richard Stallman
2005-03-23 0:59 ` Richard Stallman
2005-03-23 1:10 ` David Kastrup
2005-03-23 10:07 ` Kim F. Storm
2005-03-23 11:01 ` David Kastrup
2005-03-23 22:57 ` Kim F. Storm
2005-03-23 23:00 ` Kim F. Storm
2005-03-23 23:57 ` David Kastrup
2005-03-25 6:42 ` Richard Stallman
2005-03-23 12:59 ` Juri Linkov
2005-08-10 0:19 ` Drew Adams
2005-08-10 3:42 ` Eli Zaretskii
2005-08-10 4:19 ` Drew Adams
2005-08-10 4:03 ` Juri Linkov
2005-03-21 23:20 ` Drew Adams
2005-03-22 4:57 ` Miles Bader
2005-03-22 10:51 ` David Kastrup
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=87u0n2hqrr.fsf@jurta.org \
--to=juri@jurta.org \
--cc=emacs-devel@gnu.org \
--cc=lennart.borgman.073@student.lu.se \
--cc=rms@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).