unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Kenjiro NAKAYAMA <nakayamakenjiro@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 16258@debbugs.gnu.org, Kenjiro NAKAYAMA <nakayamakenjiro@gmail.com>
Subject: bug#16258: 24.3.50; [PATCH] eww: Add new function of region-search.
Date: Fri, 27 Dec 2013 08:43:11 +0900	[thread overview]
Message-ID: <8738lftbzk.fsf@dhcp-193-97.nrt.redhat.com> (raw)
In-Reply-To: <87ha9viumj.fsf@building.gnus.org>

> Hm...  so this would just use the default search engine to search for
> whatever is in the region?

Yes, that's right. It is not big function, sorry...

> I'm not sure that that's a useful eww mode
> command, but it might be a useful global command...

Then, how about delete the key map and include the eww-search-region?
I want to know how much eww should provide its utilities like this function.

* delete
 >> +    (define-key map [(meta s)(meta s)] 'eww-search-region)

* remain
 >> +(defun eww-search-region (&optional beg end)
 >> +  (interactive "r")
 >> +  (eww (buffer-substring beg end)))


Kenjiro

larsi@gnus.org writes:

> Kenjiro NAKAYAMA <nakayamakenjiro@gmail.com> writes:
>
>> +    (define-key map [(meta s)(meta s)] 'eww-search-region)
>
> [...]
>
>> +(defun eww-search-region (&optional beg end)
>> +  (interactive "r")
>> +  (eww (buffer-substring beg end)))
>
> Hm...  so this would just use the default search engine to search for
> whatever is in the region?  I'm not sure that that's a useful eww mode
> command, but it might be a useful global command...






  reply	other threads:[~2013-12-26 23:43 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-26  3:11 bug#16258: 24.3.50;[PATCH] eww: Add new function of region-search Kenjiro NAKAYAMA
2013-12-26 13:11 ` bug#16258: 24.3.50; [PATCH] " Kenjiro NAKAYAMA
2013-12-26 13:56 ` Lars Ingebrigtsen
2013-12-26 23:43   ` Kenjiro NAKAYAMA [this message]
2013-12-27  1:46     ` Lars Ingebrigtsen
2014-01-07 23:37       ` Ted Zlatanov
2014-11-10 21:41       ` Lars Magne Ingebrigtsen
     [not found]       ` <m3h9y6g2dd.fsf@stories.gnus.org>
2014-11-11  1:36         ` Stefan Monnier
     [not found]         ` <jwvfvdqeczj.fsf-monnier+emacsbugs@gnu.org>
2014-11-11  2:42           ` Drew Adams
     [not found]           ` <15f0d58a-de8c-4aa7-b3f3-aa12662a8c58@default>
2014-11-15 20:10             ` Drew Adams
     [not found]             ` <a88c0f55-68c4-4d5d-bdc7-a480c3aea5a2@default>
2014-11-15 20:11               ` Lars Magne Ingebrigtsen
     [not found]               ` <m37fywb4vl.fsf@stories.gnus.org>
2014-11-15 20:18                 ` Drew Adams
2014-11-14  3:47 ` Lars Magne Ingebrigtsen
2014-11-14  3:49   ` Lars Magne Ingebrigtsen
2014-11-14 17:01   ` Stefan Monnier
2014-11-15 19:26     ` Lars Magne Ingebrigtsen
2014-11-17 14:05       ` 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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8738lftbzk.fsf@dhcp-193-97.nrt.redhat.com \
    --to=nakayamakenjiro@gmail.com \
    --cc=16258@debbugs.gnu.org \
    --cc=larsi@gnus.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.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).