From: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: [drew.adams@oracle.com: links in Help buffer aren'talwayscorrect]
Date: Fri, 23 Dec 2005 19:47:26 +0200 [thread overview]
Message-ID: <ud5jniu35.fsf@gnu.org> (raw)
In-Reply-To: <doharq$ecl$1@sea.gmane.org> (message from Kevin Rodgers on Fri, 23 Dec 2005 10:07:02 -0700)
> From: Kevin Rodgers <ihs_4664@yahoo.com>
> Date: Fri, 23 Dec 2005 10:07:02 -0700
>
> Another small simplification:
>
> > (xref-or-indent-regexp
> > (format "\\(%s\\)\\|\\(\n +\\)" xref-regexp))
> ...
> > (while (re-search-forward xref-or-indent-regexp
> nil t)
> > (cond ((and (match-beginning 1) (match-end 1))
> > (replace-match "" t t))
> > ((and (match-beginning 2) (match-end 2))
> > (replace-match "\n" t t))))
>
> could be:
>
> (xref-or-indent-regexp
> (concat xref-regexp "\\|^ +"))
> ...
> (while (re-search-forward xref-or-indent-regexp nil t)
> (replace-match "" t t)
Could you please send "diff -c" or "diff -u" style patches instead?
It is a PITA to apply such changes by hand, and on top of that, manual
patching runs a greater risk of introducing bugs.
TIA
next prev parent reply other threads:[~2005-12-23 17:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1EnQVb-00056d-Vz@fencepost.gnu.org>
2005-12-19 19:22 ` [drew.adams@oracle.com: links in Help buffer aren'talwayscorrect] Kevin Rodgers
2005-12-20 19:10 ` Kevin Rodgers
2005-12-20 19:59 ` Stefan Monnier
2005-12-23 17:07 ` Kevin Rodgers
2005-12-23 17:47 ` Eli Zaretskii [this message]
[not found] <E1Eoa6a-0004hk-QI@fencepost.gnu.org>
2005-12-20 16:09 ` Kevin Rodgers
2005-12-14 20:02 [drew.adams@oracle.com: links in Help buffer aren't alwayscorrect] Richard M. Stallman
2005-12-14 22:48 ` [drew.adams@oracle.com: links in Help buffer aren'talwayscorrect] Drew Adams
2005-12-15 1:11 ` Kevin Rodgers
2005-12-15 3:16 ` Stefan Monnier
2005-12-15 17:08 ` Richard M. Stallman
2005-12-15 4:39 ` Eli Zaretskii
2005-12-15 17:08 ` Richard M. Stallman
2005-12-16 18:53 ` 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
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=ud5jniu35.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).