unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Kevin Rodgers <kevin.d.rodgers@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: some vi equivalents please?
Date: Sat, 01 Nov 2008 07:32:58 -0600	[thread overview]
Message-ID: <gehlq2$r12$1@ger.gmane.org> (raw)
In-Reply-To: <490B1DAD.8000205@dr-qubit.org>

Toby Cubitt wrote:
> rustom wrote:
>> 1. In vi I can delete a line that contains a <pat> with
>> :g/<pat>/d
>>
>> How is this done in emacs?
> 
>   M-x query-replace-regexp
> 
> then enter "^.*<pat>.*$" as the regexp (no quotes), and leave the
> replacement blank.
> 
> 
>> 2. match-variables:
>> If I want to remove everything after the second : (in a file that has
>> 3 fields separated with two :'s)
>> I do
>> :s/\(.*\):\(.*\):.*/\1 \2
>> How do I do that in emacs?
> 
>   M-x query-replace-regexp
> 
> then "^[^:]*\(.*\):\(.*\):.*$" for the regexp, and "\1 \2" for the
> replacement (again, no quotes).
> 
> The "^" and "$" both here and above are only there to prevent the regexp
> matching across lines (unlike sed, regexp searches in an Emacs buffer
> aren't line-oriented). Depending on your file, you might get away with
> something simpler. E.g. for 2, if you know there will always be two
> colons on every line, you could use "\(.*?\):\(.*?\):.*" instead ("?"
> makes a wildcard non-greedy).
> 
> query-replace-regexp is interactive, like query-replace. I find this
> useful just to check I've got the regexps right, and then hit "!" once
> I'm happy with it to replace all the rest non-interactively. The
> non-interactive version is replace-regexp.

Good advice!

> There are no doubt many other ways to accomplish this in Emacs...

Since rustom is used to vi's noninteractive way of using sed-like
commands:

C-M-h	; mark-whole-buffer
C-u M-| ; shell-command-on-region
sed '/<pat>/d'

C-M-h	; mark-whole-buffer
C-u M-| ; shell-command-on-region
sed 's/^\([^:]*\):\([^:]*\):.*$/\1 \2/'	; note the trailing /

-- 
Kevin Rodgers
Denver, Colorado, USA





  reply	other threads:[~2008-11-01 13:32 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-31 15:08 some vi equivalents please? rustom
2008-10-31 15:01 ` Toby Cubitt
2008-11-01 13:32   ` Kevin Rodgers [this message]
2008-11-01 18:47     ` Reiner Steib
2008-10-31 15:53 ` Teemu Likonen
2008-10-31 15:59 ` Drew Adams
2008-10-31 16:01 ` Parker, Matthew
2008-10-31 16:53 ` Giorgos Keramidas
2008-10-31 17:22   ` Joost Kremers
2008-10-31 17:34     ` Giorgos Keramidas
2008-10-31 22:49       ` Xah
     [not found] ` <mailman.2577.1225468814.25473.help-gnu-emacs@gnu.org>
2008-11-01 14:45   ` rustom
2008-11-01 14:52     ` rustom
2008-11-01 16:40       ` Giorgos Keramidas
2008-11-01 17:07     ` Drew Adams
     [not found]     ` <mailman.2646.1225559243.25473.help-gnu-emacs@gnu.org>
2008-11-02 15:30       ` rustom
2008-11-02 16:12         ` Drew Adams
     [not found]         ` <mailman.2710.1225642363.25473.help-gnu-emacs@gnu.org>
2008-11-03  7:19           ` rustom
2008-11-03  9:10             ` Drew Adams
2008-11-03 16:24             ` Giorgos Keramidas
2008-11-05 13:41 ` Ken Goldman
2008-11-06  7:08   ` rustom
2008-11-06 16:50     ` Drew Adams
2008-11-07 17:12       ` Johan Bockgård
2008-11-07 17:38         ` Drew Adams

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='gehlq2$r12$1@ger.gmane.org' \
    --to=kevin.d.rodgers@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).