Gnus development mailing list
 help / color / mirror / Atom feed
From: Emanuel Berg <moasen@zoho.com>
To: ding@gnus.org
Subject: Re: gnus-exit-group-hook
Date: Mon, 18 Dec 2017 20:46:26 +0100	[thread overview]
Message-ID: <86k1xjhl9p.fsf@zoho.com> (raw)
In-Reply-To: <87bmivlwy1.fsf@ericabrahamsen.net>

Eric Abrahamsen wrote:

> I guess it's just a matter of what you might
> want to use the hook for. Some people might
> want to use it to short-circuit the
> update process.

The "feelingly" inconsistent state with buffers
all over the place and changes that are done
but then reoccurs the next time you check was
a source of constant confusion/frustration in
my early Gnus days. Without understanding it,
really, I made a lot of in-between functions to
force it into what I suspect is a very
heavy-handed mold, but rather that then doing
things with the sensation maybe it isn't really
done, or maybe it is, and something else isn't,
and what have you.

Here is a Summary buffer example:

    (defun gnus-summary-exit-and-update-group ()
      (interactive)
      (kill-buffer)
      (gnus-summary-save-newsrc)
      (gnus-switch-to-group-buffer) ) ; [1]

Here is all my other Gnus [2]. If anyone wants
to wade thru it, in search of the odd nugget,
or likewise "hey, that isn't necessary",
feel free.

(prolonged silence)

OK, so no one wants to do that. Why not?!

[1] http://user.it.uu.se/~embe8573/emacs-init/gnus/summary.el
[2] http://user.it.uu.se/~embe8573/emacs-init/gnus/

-- 
underground experts united
http://user.it.uu.se/~embe8573




  reply	other threads:[~2017-12-18 19:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-18  3:29 gnus-exit-group-hook Bob Newell
2017-12-18 18:20 ` gnus-exit-group-hook Eric Abrahamsen
2017-12-18 19:46   ` Emanuel Berg [this message]
2017-12-18 23:41     ` gnus-exit-group-hook Bob Newell
2017-12-18 23:55       ` gnus-exit-group-hook Bob Newell
2017-12-19  1:40         ` gnus-exit-group-hook Eric Abrahamsen

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=86k1xjhl9p.fsf@zoho.com \
    --to=moasen@zoho.com \
    --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).