unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Sven Bretfeld <sven.bretfeld@gmx.ch>
To: help-gnu-emacs@gnu.org
Subject: Re: Why are RegExps never working?
Date: Mon, 12 Nov 2007 10:53:21 +0100	[thread overview]
Message-ID: <87abpju6we.fsf@kamaloka.dhatu> (raw)
In-Reply-To: <17FA1AE1-21E0-4816-B033-131DF93C2EDF@Web.DE> (Peter Dyballa's message of "Mon, 12 Nov 2007 10:39:43 +0100")


[-- Attachment #1.1: Type: text/plain, Size: 882 bytes --]

Hi Peter

Peter Dyballa <Peter_Dyballa@Web.DE> writes:

> Am 12.11.2007 um 00:24 schrieb Sven Bretfeld:
>
>> Sometimes I search and replace longer regexps
>> and wonder why some are always skipped. Now I understand: these are
>> the ones extending over more than one line.
>
> Have you thought of using longlines? As far as I understand it
> presents you in GNU Emacs lines formatted to the width of the window
> or frame while in the buffer (or file) the lines have the length of a
> whole paragraph ...

That would be quite inconvenient for other editing operations. My
files are usually quite unpredictable, since they come from different
authors writing in MS-Word. People seem to do very strange things when
they work with Word. So much of the editing must be done by
hand. But it might be a good idea to do at least the standard
replacements with long lines.

Greetings

Sven

[-- Attachment #1.2: Type: application/pgp-signature, Size: 188 bytes --]

[-- Attachment #2: Type: text/plain, Size: 152 bytes --]

_______________________________________________
help-gnu-emacs mailing list
help-gnu-emacs@gnu.org
http://lists.gnu.org/mailman/listinfo/help-gnu-emacs

  reply	other threads:[~2007-11-12  9:53 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-11 14:06 Why are RegExps never working? Sven Bretfeld
2007-11-11 14:47 ` Peter Dyballa
2007-11-11 15:19   ` Sven Bretfeld
2007-11-11 15:52     ` Peter Dyballa
2007-11-11 23:24       ` Sven Bretfeld
2007-11-12  9:39         ` Peter Dyballa
2007-11-12  9:53           ` Sven Bretfeld [this message]
     [not found]       ` <mailman.3307.1194823515.18990.help-gnu-emacs@gnu.org>
2007-11-12  8:21         ` Harald Hanche-Olsen
2007-11-12  9:55           ` Sven Bretfeld
2007-11-12 10:15             ` Lennart Borgman (gmail)
2007-11-12 15:10               ` Drew Adams
2007-11-12 16:01                 ` Sven Bretfeld
     [not found]           ` <mailman.3326.1194861370.18990.help-gnu-emacs@gnu.org>
2007-11-12 13:04             ` Richard G Riley
2007-11-12 18:54               ` Drew Adams
2007-11-13  8:55           ` Tim X
2007-11-13 13:54             ` Richard G Riley
     [not found]     ` <mailman.3268.1194797266.18990.help-gnu-emacs@gnu.org>
2007-11-12 23:53       ` Giorgos Keramidas
2007-11-13 15:49         ` Peter Dyballa
2007-11-13 16:37           ` Giorgos Keramidas
2007-11-13 23:51             ` Sven Bretfeld
2007-11-14  9:55               ` Peter Dyballa
2007-11-14 17:52                 ` Sven Bretfeld
     [not found]             ` <mailman.3482.1194997914.18990.help-gnu-emacs@gnu.org>
2007-11-14  3:13               ` Giorgos Keramidas
2007-11-14  9:22         ` Johan Bockgård
2007-11-16  5:15           ` Tim X
2007-11-16 10:17             ` Johan Bockgård
2007-11-11 15:21 ` Bastien
2007-11-11 14:38   ` Sven Bretfeld

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=87abpju6we.fsf@kamaloka.dhatu \
    --to=sven.bretfeld@gmx.ch \
    --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).