Gnus development mailing list
 help / color / mirror / Atom feed
From: Bastien <bzg@altern.org>
Subject: Re: Gnus (real) bookmarks
Date: Tue, 20 Jun 2006 12:11:30 +0100	[thread overview]
Message-ID: <878xns84kd.fsf@tallis.ilo.ucl.ac.uk> (raw)
In-Reply-To: <v9ejxl3zo0.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Mon, 19 Jun 2006 17:58:39 +0200")

Reiner Steib <reinersteib+gmane@imap.cc> writes:

>> M R m ?
>
> Did you suggest "R" because of the existing bindings for
> `bookmark-*' or is there some other rationale?

Yes.

> It would be nice to integrate the current `gnus-summary-*-bookmark'
> functions into your code (i.e. jump to a specific place within an
> article).

I'll work on that, good idea.

> As for the key bindings, we might steal `M B' (or even `M b'?) and
> use it as prefix for all `gnus-bookmark-*' and
> `gnus-summary-*-bookmark' commands.  What do people think?

I would suggest these bindings:

M b		gnus-summary-set-bookmark
M B		gnus-summary-remove-bookmark
C-u M b         gnus-bookmark-set
C-u M B         gnus-bookmark-delete (see below)
M j             gnus-bookmark-jump
M l             gnus-bookmark-bmenu list

> `gnus-bookmark-jump' and `gnus-bookmark-bmenu-list' should probably
> be available also from the Group buffer.

Surprisingly enough, `M l' `M j' are still free, both in the Summary
and the Group buffers.

But maybe you prefer not to mix gnus-summary-*-bookmark and
gnus-bookmark-*.

> I've installed this version with some modifications:

Thanks.

> Currently it doesn't work on Emacs 21 and XEmacs 21.4 because of
> incompatible use of `split-string' and `assoc-string'.  This should
> be fixed.

Right, i'll do that.

> - Maybe we should initialize the defcustoms from the corresponding
>   `bookmark.el' variables?

Okay.

> - WIBNI there was a command `gnus-bookmark-delete' (without using
>   `gnus-bookmark-bmenu-list')?

Was on my todo list.  I guess `gnus-bookmark-delete' will delete the
*real* bookmark, not the position set with `M b' if any.

> - `gnus-bookmark-bmenu-delete' should error out when not called from
>   the right buffer (*Gnus Bookmark List*).

Right.  I'll fix it.

> But in the entry for "EMACS MUSE" there is still the wrong name.
> The Copyright Administrator should fix this.

I will send another e-mail to double-check this issue.

-- 
Bastien



  reply	other threads:[~2006-06-20 11:11 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-30 17:00 Bastien
2006-04-30 17:08 ` Christoph Conrad
2006-04-30 17:20 ` Bastien
2006-04-30 17:31   ` Lars Magne Ingebrigtsen
2006-04-30 17:41     ` Bastien
2006-04-30 18:20       ` Romain Francoise
2006-04-30 18:32         ` Bastien
2006-04-30 18:45           ` Romain Francoise
2006-04-30 18:47             ` Bastien
2006-06-18 17:16       ` Reiner Steib
2006-06-19 12:13         ` Bastien
2006-06-19 15:58       ` Reiner Steib
2006-06-20 11:11         ` Bastien [this message]
2006-06-20 13:07           ` Reiner Steib
2006-06-20 13:50             ` Bastien
2006-08-18  9:13         ` Katsumi Yamaoka
2006-08-18 10:08           ` Reiner Steib
2006-08-18 10:23             ` Katsumi Yamaoka

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=878xns84kd.fsf@tallis.ilo.ucl.ac.uk \
    --to=bzg@altern.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).