Gnus development mailing list
 help / color / mirror / Atom feed
From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Cc: emacs-w3m@namazu.org
Subject: [emacs-w3m:11216] Re: right clicking on URL in emacs-w3m vs. gnus
Date: Thu, 22 Apr 2010 10:48:52 +0900	[thread overview]
Message-ID: <b4mochcb6kb.fsf@jpl.org> (raw)
In-Reply-To: <87iq7kc2bd.fsf@lifelogs.com>

>>>>> Ted Zlatanov wrote:
[...]
> Maybe Treatment, Article, and Commands should precede the w3m menu, and
> they should always show up on a right-click?

> Can we also hang the w3m menu in the menubar when HTML is rendered in
> the article buffer?

Hm, if what OP wishes is the *w3m* menu, though I'm still hard to
imagine what menu items should be there, I don't want it.  I only
tried a way to implement the right-click menu in an article of
*plain text* , not html.  It will be helpful to users if there are
really useful items that should be in the menu, but now it's enough
to me to press the middle button or type `M-x w3m' on a string
that looks like url. ;-)

> I'm OK with any changes you think are appropriate here, these are just
> suggestions.

> You could make a "yamaoka-dev" branch and push it with any proposed
> changes instead of a patch (the commit e-mail will still go out and we
> can see your changes in the e-mail). Then we can try the feature
> (collaboratively making changes to yamaoka-dev in the process) and merge
> it into the master branch when it's ready and you can then delete
> yamaoka-dev.  I don't know if that's the right model for us so feel free
> to propose something else if you think it's better.

Ok.  I agree it's more efficient to make a branch rather than to
post a big patch to everyone.



  reply	other threads:[~2010-04-22  1:48 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-17 22:41 [emacs-w3m:11211] " jidanni
2010-04-20 17:20 ` Ted Zlatanov
2010-04-21  6:08   ` [emacs-w3m:11213] " Katsumi Yamaoka
2010-04-21 14:23     ` Ted Zlatanov
2010-04-22  1:48       ` Katsumi Yamaoka [this message]
2010-04-23  0:01         ` Ted Zlatanov
2010-06-25 13:24           ` Štěpán Němec
2010-06-27 23:25             ` [emacs-w3m:11246] " Katsumi Yamaoka
2010-06-28  7:58               ` Štěpán Němec
2010-06-29  1:36                 ` [emacs-w3m:11248] " Katsumi Yamaoka
2010-06-29  8:57                   ` [emacs-w3m:11249] " Štěpán Němec
2010-06-30  0:28                     ` [emacs-w3m:11250] " jidanni
2010-07-28  8:33                   ` [emacs-w3m:11248] " Štěpán Němec
2010-08-05 14:47                     ` Ted Zlatanov

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=b4mochcb6kb.fsf@jpl.org \
    --to=yamaoka@jpl.org \
    --cc=ding@gnus.org \
    --cc=emacs-w3m@namazu.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).