From: Nikolaus Rath <Nikolaus@rath.org>
To: ding@gnus.org
Subject: Re: How to change definition of gnus-summary-exit?
Date: Thu, 15 Oct 2015 16:27:47 -0700 [thread overview]
Message-ID: <87d1wf4sr0.fsf@vostro.rath.org> (raw)
In-Reply-To: <8737xcndrd.fsf@gnu.org> (Tassilo Horn's message of "Thu, 15 Oct 2015 21:16:38 +0200")
On Oct 15 2015, Tassilo Horn <tsdh@gnu.org> wrote:
> Nikolaus Rath <Nikolaus@rath.org> writes:
>
>>>>> What is happening here? Why does the help refer me to the modified
>>>>> version, but the version in memory is actually the original one? And
>>>>> how do I tell emacs/gnus to use my version?
>>>
>>> Why do you copy the complete gnus-sum.el when you just want to
>>> change one function? As a result, you won't see any future changes of
>>> gnus-sum.el (bugfixes and new features).
>>
>> Not quite, the 'modified version' is actually a clone of the gnus git
>> repo.
>
> Ah, I see. Well, then I'd just use the complete git version if I were
> you.
That's what I'm trying to do. Isn't putting the lisp/ directory from the
git clone sufficient to achieve that?
>>> What do you want to change exactly? Oftentimes, a simple advice will
>>> do without having to override the complete function.
>>
>> What's an advice (in this context)?
>
> An advice is a function which is run before, after, instead of, or
> "around" some other function. See (info "(elisp)Advising Functions").
Uh, that's pretty cool. It seems I need to do some reading.
Best,
-Nikolaus
--
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
»Time flies like an arrow, fruit flies like a Banana.«
next prev parent reply other threads:[~2015-10-15 23:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-14 17:28 Nikolaus Rath
2015-10-14 18:08 ` Adam Sjøgren
2015-10-15 6:34 ` Tassilo Horn
2015-10-15 17:47 ` Nikolaus Rath
2015-10-15 19:16 ` Tassilo Horn
2015-10-15 23:27 ` Nikolaus Rath [this message]
2015-10-16 7:19 ` Tassilo Horn
2015-10-15 20:17 ` Emanuel Berg
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=87d1wf4sr0.fsf@vostro.rath.org \
--to=nikolaus@rath.org \
--cc=ding@gnus.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 NNTP newsgroup(s).