all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Noam Postavsky <npostavs@users.sourceforge.net>
Cc: Stromeko@nexgo.de, 25445@debbugs.gnu.org
Subject: bug#25445: Bug (Trunk): Redirect fails in Duckduckgo
Date: Mon, 16 Jan 2017 21:24:35 +0200	[thread overview]
Message-ID: <838tqaajv0.fsf@gnu.org> (raw)
In-Reply-To: <CAM-tV-9vdjeoX6pg4mwSPDKtr5k6HD9PrEuaHfb2S5Kz9p6EPA@mail.gmail.com> (message from Noam Postavsky on Mon, 16 Jan 2017 13:24:08 -0500)

> From: Noam Postavsky <npostavs@users.sourceforge.net>
> Date: Mon, 16 Jan 2017 13:24:08 -0500
> Cc: 25445@debbugs.gnu.org
> 
> On Mon, Jan 16, 2017 at 1:12 PM, Achim Gratz <Stromeko@nexgo.de> wrote:
> > npostavs@users.sourceforge.net writes:
> >>        (when (or (string-match "^\\([0-9]+\\) *;.*url=\"\\([^\"]+\\)\"" refresh)
> >> +                (string-match "^\\([0-9]+\\) *;.*url=\'\\([^\']+\\)\'" refresh)
> >>                  (string-match "^\\([0-9]+\\) *;.*url=\\([^ ]+\\)" refresh))
> >
> > Why not use a regex with alternatives and do just a single match?
> 
> Stefan made the same suggestion:
> https://lists.gnu.org/archive/html/emacs-devel/2017-01/msg00268.html
> 
> I'm not entirely sure it's an improvement.

Neither am I: it would make the regexp harder to interpret (for
humans).





      reply	other threads:[~2017-01-16 19:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-14  5:34 bug#25445: Bug (Trunk): Redirect fails in Duckduckgo Ian Dunn
2017-01-14  7:13 ` npostavs
2017-01-14 14:34   ` Ian Dunn
2017-01-16  0:35     ` npostavs
2017-01-16  3:33       ` Eli Zaretskii
2017-01-16  4:27         ` npostavs
2017-01-16 18:12       ` Achim Gratz
2017-01-16 18:24         ` Noam Postavsky
2017-01-16 19:24           ` Eli Zaretskii [this message]

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=838tqaajv0.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=25445@debbugs.gnu.org \
    --cc=Stromeko@nexgo.de \
    --cc=npostavs@users.sourceforge.net \
    /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.