Gnus development mailing list
 help / color / mirror / Atom feed
From: Bastien <bzg@altern.org>
To: ding@gnus.org, Stefan Monnier <monnier@iro.umontreal.ca>,
	Karl Fogel <kfogel@red-bean.com>,
	Tassilo Horn <tassilo@member.fsf.org>,
	emacs-devel@gnu.org
Subject: Re: bookmark.el and lisp/gnus/gnus-bookmark.el
Date: Sat, 08 Mar 2008 11:56:54 +0000	[thread overview]
Message-ID: <8763vx77jt.fsf@bzg.ath.cx> (raw)
In-Reply-To: <v97igdjvo1.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Sat, 08 Mar 2008 12:35:10 +0100")

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

> Do I understand correctly that after changing gnus-bookmark.el, it
> will take advantage of new features in bookmark.el that are not
> present in Emacs < 23.  I.e. it wont work in Emacs 22 at all (and
> XEmacs?).

Yes.

> As `gnus-bookmark.el' is quite new in No Gnus, I don't expect many
> Emacs <= 22 users use it intensively.  If it is not too much work, it
> would be nice to make it work for all supported Emacsen, cf. (info
> "(gnus)Emacsen").  But I don't insist on this.  

I think this is too much work, and as you said, not that many people
might be using this feature.

The only thing is this: gnus-bookmark.el was good to get Gnus bookmarks
and *only* them.  This will go away with the new gnus-bookmark.el.  So,
since the new feature of bookmark.el will help many modes provide their
own ways of setting a bookmark, I think it would make sense to have a
"type" key in the bookmark record (similar to the annotation), and be
able to list bookmarks of a certain type only.

C-u C-x r l [Prompt type] Info RET 
  => list bookmark of Info type

C-u C-x r l [Prompt type] Gnus RET 
  => list Gnus bookmarks

If you think it is a good idea, I will do it.

> If you don't support
> Emacs < 23, please ...
>
> - document that only Emacs 23 and up are supported,
>
> - make sure that it doesn't disturb compiling Gnus with Emacs < 23 too
>   much,
>
> - signal appropriate errors when trying to use it in Emacs < 23.

Ok, will do this.

-- 
Bastien




      reply	other threads:[~2008-03-08 11:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <874pbj682f.fsf@red-bean.com>
     [not found] ` <jwv4pbjd7wo.fsf-monnier+emacs@gnu.org>
     [not found]   ` <87zltbhbq8.fsf@bzg.ath.cx>
     [not found]     ` <jwvlk4vwo1x.fsf-monnier+emacs@gnu.org>
     [not found]       ` <87iqzzigv6.fsf@bzg.ath.cx>
     [not found]         ` <87ejan7xhq.fsf@member.fsf.org>
     [not found]           ` <87hcfi3egg.fsf@bzg.ath.cx>
     [not found]             ` <87abla8w6b.fsf@member.fsf.org>
     [not found]               ` <87bq5qhba6.fsf@bzg.ath.cx>
     [not found]                 ` <871w6m8t59.fsf@member.fsf.org>
     [not found]                   ` <87ablamphg.fsf@red-bean.com>
     [not found]                     ` <87skz2lacp.fsf@bzg.ath.cx>
     [not found]                       ` <87tzjil9oz.fsf@red-bean.com>
     [not found]                         ` <8763vyl964.fsf@bzg.ath.cx>
     [not found]                           ` <jwvtzjiw6ic.fsf-monnier+emacs@gnu.org>
     [not found]                             ` <874pbiypad.fsf@bzg.ath.cx>
2008-03-08 11:35                               ` Reiner Steib
2008-03-08 11:56                                 ` Bastien [this message]

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=8763vx77jt.fsf@bzg.ath.cx \
    --to=bzg@altern.org \
    --cc=ding@gnus.org \
    --cc=emacs-devel@gnu.org \
    --cc=kfogel@red-bean.com \
    --cc=monnier@iro.umontreal.ca \
    --cc=tassilo@member.fsf.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).