unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Tassilo Horn <tassilo@member.fsf.org>
To: Le Wang <l26wang@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: possible `with-current-buffer' bug
Date: Mon, 07 Feb 2011 10:43:00 +0100	[thread overview]
Message-ID: <87y65s6uzf.fsf@member.fsf.org> (raw)
In-Reply-To: <AANLkTinyZhmzox4_5MCp0oqAvxP-7PvPPY5qFWQ8_aQ1@mail.gmail.com> (Le Wang's message of "Mon, 7 Feb 2011 17:23:09 +0800")

Le Wang <l26wang@gmail.com> writes:

> It lets you grep through a list of files.  Files may contain space in
> their names.  The most important thing is concatenated length of the
> file names is not a restricting factor.  i.e. grep unlimited number of
> files.

If `rgrep' and friends don't allow whitespaces in filenames and hit the
command line limit much earlier than your version, I'd consider it a bug
that should be reported using M-x report-emacs-bug.  But since `rgrep'
uses `find' (or, on Windows, the find emulation of dired) in conjunction
with -print0, it shouldn't suffer problems with filenames with spaces or
maximum length of command lines...

> I'm not sure what the command line length limit is for other OS, but
> on Vista, it's pretty short.

On my Gentoo/GNU Linux box, it is...

--8<---------------cut here---------------start------------->8---
% getconf ARG_MAX
2097152
--8<---------------cut here---------------end--------------->8---

Bye,
Tassilo



  reply	other threads:[~2011-02-07  9:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-06 17:30 possible `with-current-buffer' bug Le Wang
2011-02-06 19:10 ` Stephen Berman
2011-02-07  7:26   ` Le Wang
2011-02-07  8:44     ` Tassilo Horn
2011-02-07  9:23       ` Le Wang
2011-02-07  9:43         ` Tassilo Horn [this message]
2011-02-07  9:44         ` Thierry Volpiatto
2011-02-07 10:16         ` Eli Zaretskii
2011-02-07 12:10           ` Le Wang

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=87y65s6uzf.fsf@member.fsf.org \
    --to=tassilo@member.fsf.org \
    --cc=help-gnu-emacs@gnu.org \
    --cc=l26wang@gmail.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).