Gnus development mailing list
 help / color / mirror / Atom feed
From: sigurd@12move.de (Karl Pflästerer)
Subject: Better definition for `gnus-article-refer-article'
Date: Wed, 19 Feb 2003 22:41:06 +0100	[thread overview]
Message-ID: <m3znoskl7d.fsf@hamster.pflaesterer.de> (raw)

Hi,
I noticed that the buttons react at the moment smarter if you press them
at a message-id in the article buffer than `gnus-article-refer-article'.
I looked at the definition for that function and wrote it a bit
different. What do you mean? IMO I must have forgotten something because
it seems to easy. I don't think it's necessary to check if we have a
message-id around point because a user would only use that function for
a message-id.

(defun gnus-article-refer-article ()
  "Read article specified by message-id around point."
  (interactive)
  (let ((point (point)) message-id)
    (re-search-backward "<?news:\\|<" nil t)
    (cond ((re-search-forward gnus-button-mid-or-mail-regexp nil t)
	    (setq message-id (concat "<" (match-string 0) ">"))
	    (goto-char point)
	    (set-buffer gnus-summary-buffer)
	    (gnus-summary-refer-article message-id))
	  (t
	    (goto-char point)
	    (error "No references around point")))))

bye
   KP

-- 
    'Twas brillig, and the slithy toves
        Did gyre and gimble in the wabe;
    All mimsy were the borogoves,
         And the mome raths outgrabe.   "Lewis Carroll" "Jabberwocky"



             reply	other threads:[~2003-02-19 21:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-19 21:41 Karl Pflästerer [this message]
2003-02-20 10:06 ` Kai Großjohann
2003-02-20 13:08   ` Karl Pflästerer
2003-02-21 17:59     ` Proposed patch (was: Better definition for `gnus-article-refer-article') Karl Pflästerer
2003-02-21 21:12       ` Proposed patch Kai Großjohann
2003-02-21 21:58         ` Karl Pflästerer
2003-03-01 22:48           ` Jesper Harder
2003-02-21 22:02         ` Karl Pflästerer
2003-02-22 10:38           ` Kai Großjohann
2003-02-22 13:31       ` Kai Großjohann

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=m3znoskl7d.fsf@hamster.pflaesterer.de \
    --to=sigurd@12move.de \
    /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).