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

On Thu, Mar 06 2008, Bastien wrote:
> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> Karl Fogel:
>>>   ;; This file implements real bookmarks for Gnus, closely following the way
>>>   ;; `bookmark.el' handles bookmarks.  Most of the code comes from
>>>   ;; `bookmark.el'.
>>> I'm not sure why GNUS bookmarks should live in a separate space from
>>> other bookmarks, and my feeling is that they ought to be unified --
>> Indeed, it seems worthwhile to merge them, tho I've never used
>> gnus-bookmarks.  Bastien?
> Two answers: yes gnus-bookmarks.el should stored Gnus bookmarks in
> ~/.emacs.bmk (as every mode should do), but no we can't get rid of
> gnus-bookmarks.el because it adds some keybindings to Gnus.

On Sat, Mar 08 2008, Bastien wrote:
> Following Karl advice I've applied a different patch.  There is now
> `bookmark-make-name-function' *and* `bookmark-make-record-function',
> both buffer local.  For an example on how this is supposed to work 
> look at the changes I've made in info.el.  
>
> I think it's okay like this.  If you plan to change anything please 
> tell me before I work on gnus-bookmark.el. 

I didn't follow this discussion closely.  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?).

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.  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.

Bye, Reiner.

P.S.: Please strip me from further CC's (I read the list(s));
      instead include ding@gnus.org if the discussion is Gnus-related.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/




       reply	other threads:[~2008-03-08 11:35 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 [this message]
2008-03-08 11:56                                 ` Bastien

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=v97igdjvo1.fsf@marauder.physik.uni-ulm.de \
    --to=reinersteib+gmane@imap.cc \
    --cc=Reiner.Steib@gmx.de \
    --cc=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).