emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@gnu.org>
To: "François Pinard" <pinard@iro.umontreal.ca>
Cc: emacs-orgmode@gnu.org
Subject: Re: gnus: link annoyance
Date: Tue, 07 Jan 2014 10:00:29 +0100	[thread overview]
Message-ID: <87iotwp3o2.fsf@bzg.ath.cx> (raw)
In-Reply-To: <87ha9g2w1p.fsf@iro.umontreal.ca> ("François Pinard"'s message of "Tue, 07 Jan 2014 00:36:02 -0500")

[-- Attachment #1: Type: text/plain, Size: 555 bytes --]

Hi François,

François Pinard <pinard@iro.umontreal.ca> writes:

> One possibility (untested, so I'm not sure) is that when following a
> "gnus:" link, Org could use something like:
>
>    (let ((gnus-mark-article-hook nil))
>      (ACCESS-THE-gnus:-LINK))

I attach a patch to see if it does what you want.

This is from a quick exploration, and while testing it,
somes links to gwene.org blog entries were throwing a
501 error message (but still display the article.)

Take it as a basis for clarifying the discussion, not
really a solution right now!


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: org-gnus-display-article.patch --]
[-- Type: text/x-diff, Size: 898 bytes --]

diff --git a/lisp/org-gnus.el b/lisp/org-gnus.el
index e368a14..968c556 100644
--- a/lisp/org-gnus.el
+++ b/lisp/org-gnus.el
@@ -262,7 +262,7 @@ If `org-store-link' was called with a prefix arg the meaning of
 	       (cond
 		((eq backend 'nndoc)
 		 (if (gnus-group-read-group t nil group)
-		     (gnus-summary-goto-article article nil t)
+		     (gnus-summary-display-article article)
 		   (message "Couldn't follow gnus link.  %s"
 			    "The summary couldn't be opened.")))
 		(t
@@ -283,7 +283,7 @@ If `org-store-link' was called with a prefix arg the meaning of
 					(1+ articles)
 				      (* articles 2))))
 		   (if group-opened
-		       (gnus-summary-goto-article article nil t)
+		       (gnus-summary-display-article article)
 		     (message "Couldn't follow gnus link.  %s"
 			      "The summary couldn't be opened."))))))
 	   (quit (message "Couldn't follow gnus link.  %s"

[-- Attachment #3: Type: text/plain, Size: 14 bytes --]


-- 
 Bastien

  reply	other threads:[~2014-01-07  9:00 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-06 13:48 gnus: link annoyance François Pinard
2014-01-06 16:39 ` Nick Dokos
2014-01-07  5:14   ` François Pinard
2014-01-07 12:07     ` Nick Dokos
2014-01-07 15:28       ` François Pinard
2014-01-07 19:06         ` Achim Gratz
2014-01-08  1:37           ` François Pinard
2014-01-08 15:15             ` Bastien
2014-01-06 17:05 ` Rasmus
2014-01-07  5:36   ` François Pinard
2014-01-07  9:00     ` Bastien [this message]
2014-01-07 14:13       ` François Pinard
2014-01-07 13:01     ` Rasmus
2014-01-07 14:34       ` François Pinard
2014-01-07 13:28     ` Joseph Vidal-Rosset
2014-01-07 15:02       ` François Pinard
2014-01-07 17:09         ` Joseph Vidal-Rosset
2014-01-07 17:43           ` Nick Dokos

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=87iotwp3o2.fsf@bzg.ath.cx \
    --to=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=pinard@iro.umontreal.ca \
    /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).