From: Ulf Stegemann <ulf-news@zeitform.de>
To: emacs-orgmode@gnu.org
Subject: Re: [PATCH] better links to Gnus articles
Date: Fri, 28 Nov 2008 15:58:29 +0100 [thread overview]
Message-ID: <zf.upnej0vx5gq.fsf@zeitform.de> (raw)
In-Reply-To: 87myfki45i.fsf@thinkpad.tsdh.de
Tassilo Horn <tassilo@member.fsf.org> wrote:
> Ulf Stegemann <ulf-news@zeitform.de> writes:
>
>> I've just updated to the latest git version and it seems that the
>> patch in questions breaks linking to Gnus articles. I'm using XEmacs
>> 21.4.21 and No Gnus v0.9.
>
> Hm, I tried to setup XEmacs 21.4.21 and ngnus-0.10 (0.9 is not listed at
> gnus.org), but when do (require 'gnus) I get:
>
> Debugger entered--Lisp error: (file-error "Cannot open load file"
> "jka-compr")
[...]
> Where do I get jka-compr for XEmacs?
It's part of the 'os-utils' package.
> Hm, that indicates that `org-gnus-store-link' returned nil. You could
> do me a favour and edebug `org-gnus-store-link' and see what's going
> wrong. There might me some differences between emacs and XEmacs I'm not
> aware of.
In fact org-gnus wasn't even loaded. The reason was that XEmacs'
`defvaralias' (line 41) doesn't accept an optional third argument as
Emacs does. Once this had been fixed, org-gnus was loaded without
problems and worked right away.
While testing the new version I've noticed that links are now made up of
<group>#<message-id> instead of <group>#<article number>, at least for
nnml groups. This means that links created with the new version are not
usable with older versions. And this might be a problem since the same set
of org files is often used on different computers with possibly
different versions of org-mode.
Ulf
next prev parent reply other threads:[~2008-11-28 14:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-19 7:49 [PATCH] better links to Gnus articles Tassilo Horn
2008-11-19 11:27 ` Carsten Dominik
2008-11-27 16:12 ` Ulf Stegemann
2008-11-28 9:35 ` Tassilo Horn
2008-11-28 14:58 ` Ulf Stegemann [this message]
2008-11-30 8:52 ` Carsten Dominik
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=zf.upnej0vx5gq.fsf@zeitform.de \
--to=ulf-news@zeitform.de \
--cc=emacs-orgmode@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).