From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/69632 Path: news.gmane.org!not-for-mail From: Katsumi Yamaoka Newsgroups: gmane.emacs.w3m,gmane.emacs.gnus.general Subject: [emacs-w3m:11216] Re: right clicking on URL in emacs-w3m vs. gnus Date: Thu, 22 Apr 2010 10:48:52 +0900 Organization: Emacsen advocacy group Message-ID: References: <87sk6thfcc.fsf@jidanni.org> <87sk6qf3bu.fsf@lifelogs.com> <87iq7kc2bd.fsf@lifelogs.com> Reply-To: emacs-w3m@namazu.org NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: dough.gmane.org 1271900963 27844 80.91.229.12 (22 Apr 2010 01:49:23 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Thu, 22 Apr 2010 01:49:23 +0000 (UTC) Cc: emacs-w3m@namazu.org To: ding@gnus.org Original-X-From: emacs-w3m-admin@namazu.org Thu Apr 22 03:49:21 2010 connect(): No such file or directory Return-path: Envelope-to: emacs-w3m@deer.gmane.org Original-Received: from quimby.gnus.org ([80.91.231.51]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1O4lXd-0000Ys-5a for emacs-w3m@deer.gmane.org; Thu, 22 Apr 2010 03:49:21 +0200 Original-Received: from vaj.namazu.org ([202.221.179.42]) by quimby.gnus.org with esmtp (Exim 3.36 #1 (Debian)) id 1O4lXc-0001ib-00 for ; Thu, 22 Apr 2010 03:49:20 +0200 Original-Received: from vaj.namazu.org (localhost [127.0.0.1]) by vaj.namazu.org (Postfix) with ESMTP id 7A0C599E8A; Thu, 22 Apr 2010 10:49:15 +0900 (JST) Original-Received: from orlando.hostforweb.net (orlando.hostforweb.net [216.246.45.90]) by vaj.namazu.org (Postfix) with ESMTP id 1EF0F99E2D for ; Thu, 22 Apr 2010 10:49:14 +0900 (JST) Original-Received: from localhost ([127.0.0.1]:39973) by orlando.hostforweb.net with esmtpa (Exim 4.69) (envelope-from ) id 1O4lXJ-0007sx-62; Wed, 21 Apr 2010 20:49:01 -0500 X-ML-Name: emacs-w3m X-Mail-Count: 11216 X-MLServer: fml [fml 4.0.3 release (20011202/4.0.3)]; post only (anyone can post) X-ML-Info: If you have a question, send e-mail with the body "help" (without quotes) to the address emacs-w3m-ctl@namazu.org; help= User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/24.0.50 (gnu/linux) X-Hashcash: 1:20:100422:ding@gnus.org::xXefwpj9IBamdrie:000095TG X-Hashcash: 1:20:100422:emacs-w3m@namazu.org::KVthidNMDor18Rna:000000000000000000000000000000000000000001dG/ X-Face: #kKnN,xUnmKia.'[pp`;Omh}odZK)?7wQSl"4o04=EixTF+V[""w~iNbM9ZL+.b*_CxUmFk B#Fu[*?MZZH@IkN:!"\w%I_zt>[$nm7nQosZ<3eu;B:$Q_:p!',P.c0-_Cy[dz4oIpw0ESA^D*1Lw= L&i*6&( Cancel-Lock: sha1:pewHSIT2qPnu/uMZNBhdYxgyhC4= X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - orlando.hostforweb.net X-AntiAbuse: Original Domain - namazu.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - jpl.org X-Source: X-Source-Args: X-Source-Dir: X-Spam-Flag: No X-Spam-Probability: 0.000000 Precedence: bulk Original-Lines: 29 List-Id: emacs-w3m.namazu.org List-Software: fml [fml 4.0.3 release (20011202/4.0.3)] List-Post: List-Owner: List-Help: List-Unsubscribe: Xref: news.gmane.org gmane.emacs.w3m:8575 gmane.emacs.gnus.general:69632 Archived-At: >>>>> 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.