unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: bhenz@Lexmark.com
Cc: help-gnu-emacs-bounces+bhenz=lexmark.com@gnu.org, help-gnu-emacs@gnu.org
Subject: Re: ediff naming buffers (newbie alert)
Date: Wed, 8 Mar 2006 09:36:43 -0500	[thread overview]
Message-ID: <OF9D5AE303.44E91971-ON8525712B.005016B8-8525712B.00509341@lexmark.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1789 bytes --]

Thank you!

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")

I've been pulling my hair out over this "typo" for a while now!
Thanks again,
Bob





Alan Mackenzie <acm@muc.de>
Sent by: help-gnu-emacs-bounces+bhenz=lexmark.com@gnu.org
03/07/2006 11:08 AM

 
        To:     help-gnu-emacs@gnu.org
        cc: 
        Subject:        Re: ediff naming buffers (newbie alert)


bhenz@lexmark.com wrote on Tue, 7 Mar 2006 09:45:32 -0500:
> This is a multipart message in MIME format.
> --=_alternative 005162028525712A_=
> Content-Type: text/plain; charset="us-ascii"

> Hi,

> (I running emacs 21.4.1)

> I am trying to hook into the "ediff-startup-hooks" but ediff completely 
> ignores my attemps. I have the following code in my .emacs file... 

[ .... ]

> (add-hook 'ediff-startup-hooks 'my-ediff-startup-hooks) 
                               ^
                               |
                               |
                      Please remove this "s"   :-)

> Any ideas? Does anyone have example code of doing this similar sort of
> thing.  (Preferrably something simple like just a "print" statement in
> the new startup hook?

Oh yes!  I've had code doing this sort of thing (i.e. nothing) for years!

> Thanks in advance,
> Bob

-- 
Alan Mackenzie (Munich, Germany)
Email: aacm@muuc.dee; to decode, wherever there is a repeated letter
(like "aa"), remove half of them (leaving, say, "a").

_______________________________________________
help-gnu-emacs mailing list
help-gnu-emacs@gnu.org
http://lists.gnu.org/mailman/listinfo/help-gnu-emacs



[-- Attachment #1.2: Type: text/html, Size: 3155 bytes --]

[-- Attachment #2: Type: text/plain, Size: 152 bytes --]

_______________________________________________
help-gnu-emacs mailing list
help-gnu-emacs@gnu.org
http://lists.gnu.org/mailman/listinfo/help-gnu-emacs

             reply	other threads:[~2006-03-08 14:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-08 14:36 bhenz [this message]
2006-03-08 19:04 ` ediff naming buffers (newbie alert) Kevin Rodgers
     [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=OF9D5AE303.44E91971-ON8525712B.005016B8-8525712B.00509341@lexmark.com \
    --to=bhenz@lexmark.com \
    --cc=help-gnu-emacs-bounces+bhenz=lexmark.com@gnu.org \
    --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.
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).