From: Kevin Rodgers <ihs_4664@yahoo.com>
Subject: Re: ediff naming buffers (newbie alert)
Date: Wed, 08 Mar 2006 12:04:56 -0700 [thread overview]
Message-ID: <dun9u1$47h$1@sea.gmane.org> (raw)
In-Reply-To: <OF9D5AE303.44E91971-ON8525712B.005016B8-8525712B.00509341@lexmark.com>
bhenz@Lexmark.com wrote:
> It appears that the documentation for ediff is incorrect? or else there
> are just a lot of people that have bad documentation on the web... (e.g.
> google search for ediff-startup-hooks, or go directly to
>
"http://wwwwbs.cs.tu-berlin.de/user-taipan/kraxel/gnuinfo/ediff/Hooks.html")
Why resort to the web before checking Emacs' own documentation? It
comes with an Ediff manual (in Info format) that is correct.
--
Kevin Rodgers
next prev parent reply other threads:[~2006-03-08 19:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-08 14:36 ediff naming buffers (newbie alert) bhenz
2006-03-08 19:04 ` Kevin Rodgers [this message]
[not found] <mailman.39.1141744558.2319.help-gnu-emacs@gnu.org>
2006-03-07 16:08 ` Alan Mackenzie
-- strict thread matches above, loose matches on Subject: below --
2006-03-07 14:45 bhenz
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='dun9u1$47h$1@sea.gmane.org' \
--to=ihs_4664@yahoo.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).