From: Peter Dyballa <Peter_Dyballa@web.de>
To: Aaron Meurer <asmeurer@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Mouse support does not work
Date: Wed, 11 Jan 2012 00:26:26 +0100 [thread overview]
Message-ID: <49E98AF3-7986-4495-BB39-E07D236450A0@web.de> (raw)
In-Reply-To: <CAKgW=6+2F3it9kkEdtmqty0OVC5Gvi0Qoq0QPAaiPHfrqdOMJQ@mail.gmail.com>
Am 10.1.2012 um 23:50 schrieb Aaron Meurer:
> (can the GUI version of emacs use a non-monospaced font, btw?).
Of course.
>>> - Is there a way to make scrolling not kill an I-search?
>>
>> I don't know! Why do you want to scroll in that "mode"? Because you want to centre the found text at the bottom? Then try C-l! Or press C-l twice. (Or three times...)
>
> I want to scroll around and see what's highlighted, not press C-s a
> bunch of times.
Make the window higher! You could have 100 lines displayed.
> Scrolling gives me visual feedback on where I am in
> the file that jump scrolling does not.
GNU Emacs allows to display line numbers in the mode-line. Put in the customisations section of your init file:
'(column-number-mode t)
In GNU Emacs 23.3b the variable isearch-mode-map contains some mouse events. Maybe you can add mouse-4 and mouse-5...
> This is one of the reasons I want it to scroll one line at a time.
The others?
Maybe the developers feel like me that scrolling around is a bit imprecise and you likely lose the place where isearch found the text...
--
Greetings
Pete
The human animal differs from the lesser primates in his passion for lists of "Ten Best."
– H. Allen Smith
next prev parent reply other threads:[~2012-01-10 23:26 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-10 9:18 Mouse support does not work Aaron Meurer
2012-01-10 17:24 ` Tassilo Horn
2012-01-10 18:29 ` Eli Zaretskii
2012-01-10 21:00 ` Tassilo Horn
2012-01-10 21:32 ` Peter Dyballa
2012-01-11 8:04 ` Tassilo Horn
2012-01-11 22:12 ` Peter Dyballa
2012-01-12 7:22 ` Tassilo Horn
2012-01-12 9:44 ` Peter Dyballa
2012-01-12 9:56 ` Tassilo Horn
2012-01-12 10:06 ` Peter Dyballa
2012-01-10 21:31 ` Peter Dyballa
2012-01-10 21:29 ` Peter Dyballa
2012-01-10 22:06 ` Aaron Meurer
2012-01-10 22:31 ` Peter Dyballa
2012-01-10 22:50 ` Aaron Meurer
2012-01-10 23:26 ` Peter Dyballa [this message]
2012-01-11 12:50 ` Aaron Meurer
2012-01-11 14:24 ` Drew Adams
2012-01-11 14:37 ` Drew Adams
2012-01-11 15:28 ` Aaron Meurer
2012-01-11 19:10 ` Drew Adams
2012-01-11 21:14 ` Aaron Meurer
2012-01-14 16:45 ` Aaron Meurer
2012-01-14 16:53 ` Drew Adams
2012-01-14 17:26 ` Aaron Meurer
2012-01-14 17:37 ` Drew Adams
2012-01-14 17:49 ` Aaron Meurer
2012-01-14 18:20 ` Drew Adams
2012-01-14 19:55 ` Aaron Meurer
2012-01-14 20:08 ` Drew Adams
2012-01-14 20:32 ` Aaron Meurer
2012-01-14 21:00 ` Drew Adams
2012-01-15 0:01 ` Aaron Meurer
2012-01-15 0:55 ` Peter Dyballa
2012-01-15 0:58 ` Drew Adams
2012-01-15 15:19 ` Peter Dyballa
2012-01-15 1:13 ` Aaron Meurer
2012-01-15 15:28 ` Peter Dyballa
2012-01-15 15:47 ` Aaron Meurer
2012-01-15 16:30 ` Peter Dyballa
2012-01-16 18:22 ` Aaron Meurer
2012-01-14 17:46 ` Aaron Meurer
2012-01-10 23:44 ` Peter Dyballa
2012-01-11 6:31 ` Jonathan Groll
2012-01-11 6:15 ` Jonathan Groll
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=49E98AF3-7986-4495-BB39-E07D236450A0@web.de \
--to=peter_dyballa@web.de \
--cc=asmeurer@gmail.com \
--cc=help-gnu-emacs@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).