From: K T Ligesh <ligesh@lxlabs.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Minibuffer and Dabbrev problems
Date: Wed, 18 Jun 2003 17:41:27 +0530 [thread overview]
Message-ID: <20030618121127.GD1423@lxlabs.com> (raw)
In-Reply-To: <3EEF5269.1060909@yahoo.com>
On Tue, Jun 17, 2003 at 11:39:53AM -0600, Kevin Rodgers wrote:
> K T Ligesh wrote:
>
> > 1) Minibuffer Error Messages:
> >
> > When I move around in the minibuffer, I get error messages like "End
> > of History" and the message persists for a few seconds which is
> > extremely irritating. I searched and found that the error messages
> > are -built into- the search-previous-history commands etc..
You mean, you cannot 'return' from a function without generating an error message? Elisp doesn't have a straight 'return' statement?
> > Those error messages are really screwing up my brain. Sort of like
> > speedbreakers that block my flow of thought.. So I would like some
> > help before I go completely insane...
>
> Relax, have a home brew.
Actually coming from the vim world, all these error messages are sort of strange. For a person used to just a beep, after some time, these messages can get into your head.
There should be some option for advanced users to turn off -all- error messages; they do cause certain discomfort. But I guess, that is not trivially possible. I will just have to rewrite those functions without those error messages... That will mean a lot of rewrite though....
I noticed Emacs does not try to be Keyboard efficient. Pressing 2 <C-s> to get to the next match seems almost preposterous to me. (In vim it is just an 'n' - the difference is huge) Yeah, but I guess it all depends on your view point...
Currently I am trying to implement incremental search into Viper search... As I said earlier, 2 <C-s> are too much for me..
Could somebody give me a -SIMPLE- incremental search code. The one with package is too complex for me - I am just a 12 day old toddler.
And I am repeating one of my previous requests here..
Can I map <C-d> to generate a <C-c>. It is not about -define-key-... I need to map keys one step below that... When I press <C-d> I want the upper layers (mainly the elisp modules) to think that I have pressed <C-c>. Otherwise I will have to go around and remap the <C-c> in -every- module...
Thanks for all the help...
--
:: Ligesh :: http://ligesh.com :: http://lxlabs.com ::
next prev parent reply other threads:[~2003-06-18 12:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-12 16:49 replace TAB with 8 whitespaces jinneemop
2003-06-12 17:19 ` Henrik Enberg
2003-06-12 17:26 ` Alan Mackenzie
2003-06-12 17:34 ` Peter J. Acklam
2003-06-13 7:00 ` Kai Großjohann
2003-06-16 12:51 ` jinneemop
2003-06-16 7:26 ` Kai Großjohann
2003-06-16 19:52 ` jinneemop
2003-06-16 12:36 ` Minibuffer and Dabbrev problems K T Ligesh
2003-06-16 13:17 ` replace TAB with 8 whitespaces Kai Großjohann
2003-06-16 13:53 ` Stefan Monnier
[not found] ` <mailman.7972.1055767014.21513.help-gnu-emacs@gnu.org>
2003-06-16 15:11 ` Minibuffer and Dabbrev problems Kai Großjohann
2003-06-16 17:25 ` Johan Bockgård
2003-06-16 23:02 ` K T Ligesh
2003-06-17 17:39 ` Kevin Rodgers
2003-06-18 12:11 ` K T Ligesh [this message]
[not found] ` <mailman.8150.1055940540.21513.help-gnu-emacs@gnu.org>
2003-06-18 16:33 ` Kai Großjohann
2003-06-18 19:29 ` Stefan Monnier
2003-06-18 23:30 ` Kevin Rodgers
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=20030618121127.GD1423@lxlabs.com \
--to=ligesh@lxlabs.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.