unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Thierry Volpiatto <thierry.volpiatto@gmail.com>
To: reader@newsguy.com
Cc: help-gnu-emacs@gnu.org
Subject: Re: jump between if-fi
Date: Mon, 31 Dec 2007 09:12:25 +0100	[thread overview]
Message-ID: <87ir2fuvti.fsf@dell.linuxdev.us.dell.com> (raw)
In-Reply-To: <87bq87bcn7.fsf@newsguy.com> (reader@newsguy.com's message of "Mon, 31 Dec 2007 00:29:16 -0600")

reader@newsguy.com writes:

> "Lennart Borgman (gmail)" <lennart.borgman@gmail.com> writes:
>
>> reader@newsguy.com wrote:
>>> I hope this isn't one of those things that is just plain obvious to
>>> lookup in emacs but I'm striking out with M-x apropos
>>>
>>> How can I make emacs do something similar with if-fi constructs as it
>>> does with parens?
>>>
>>> Even better I'd like the kind of behaviour one can get in vim with
>>> parens, where not only does the syntax coloring show the other paren
>>> but you can jump there with a Ctrl-%
>>
>> Maybe you mean %, not C-%?
>
> Yes I did.
>
>> You can in Emacs too, using Viper. But see
>>
>>   http://www.emacswiki.org/cgi-bin/wiki/ViKeys
>>   http://www.emacswiki.org/cgi-bin/wiki/ViAndEmacs
>>
> Thanks for those ... I knew some it but found some more.
> But no, I don't want to try to turn emacs into vi so much as turn
> emacs power loose on if-fi while-done etc constructs.
>
>>> I know emacs can do that as well but not as easily.  But anyway, I use
>>> emacs more and would like to turn its powers used in paren recognition
>>> against the `if fi', `while done', `for done'... etc. one uses in
>>> shell scripting.
>
> That was my my main question and I didn't notice anything on those
> sites about that... I hope I just missed it.
>
> So still wondering how to get paren type actions to work on if-fi type
> shell constructs.

While you are in a script shell you have keybindings for case, if, 
while getopts, etc... to construct all this statements.
If you do C-h m you will find them.
-- 
A+ Thierry
Pub key: http://pgp.mit.edu

  reply	other threads:[~2007-12-31  8:12 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-30 23:02 jump between if-fi reader
2007-12-30 23:23 ` Lennart Borgman (gmail)
2007-12-31  6:29   ` reader
2007-12-31  8:12     ` Thierry Volpiatto [this message]
2007-12-31 14:41       ` reader
2008-01-01 15:47   ` reader
     [not found]   ` <mailman.5533.1199082573.18990.help-gnu-emacs@gnu.org>
2008-01-09  5:40     ` Stefan Monnier
2007-12-31 16:24 ` Alan Mackenzie
2008-01-01  2:29   ` reader
2008-01-01 14:18     ` Alan Mackenzie
2008-01-01 15:39       ` reader
2008-01-01 15:53     ` Torturedly threaded .emacs portability. [Was: jump between if-fi] Alan Mackenzie
2008-01-01 15:53       ` reader
2008-01-02  5:00       ` Mike Mattie
2008-01-05 18:33     ` jump between if-fi reader
2008-01-09  9:43 ` Arnaldo Mandel
     [not found] <mailman.5524.1199055779.18990.help-gnu-emacs@gnu.org>
2008-01-01 18:12 ` Xah Lee
2008-01-01 19:12   ` Alan Mackenzie

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=87ir2fuvti.fsf@dell.linuxdev.us.dell.com \
    --to=thierry.volpiatto@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=reader@newsguy.com \
    /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).