From: Le Wang <l26wang@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: tassilo@member.fsf.org, help-gnu-emacs@gnu.org
Subject: Re: possible `with-current-buffer' bug
Date: Mon, 7 Feb 2011 20:10:31 +0800 [thread overview]
Message-ID: <AANLkTimP_6EyDYH=bYkRaraYivrMXC08SnWtHcOp=yV-@mail.gmail.com> (raw)
In-Reply-To: <E1PmO8m-0004gQ-AL@fencepost.gnu.org>
[-- Attachment #1: Type: text/plain, Size: 954 bytes --]
On Mon, Feb 7, 2011 at 6:16 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>
> How short is "pretty short"? It should be 32K if we invoke commands
> directly, or 8K if we do that through a Windows shell (which should
> only happen if there's a pipe in the command).
>
Actually maybe not that short. The string with all the filenames is 38k
characters. I'm not sure when exactly grep starts failing, but it takes 2
invocations of grep to process that string, so 32k sounds entirely
plausible. I'm using cygwin grep with NTEmacs with "c:\cygwin\bin\zsh.exe"
as my shell, if that's relevant.
Since I already have the list of files, doing grep this way is really fast.
I don't expect this is a use-case that comes up often for everyone, but if
anyone looks for something similar in the future, hopefully this helps.
Also, despite what I've implied, Emacs' grep family of functions have very
good support for whitespaces. Sorry about the confusion.
--
Le
[-- Attachment #2: Type: text/html, Size: 1316 bytes --]
prev parent reply other threads:[~2011-02-07 12:10 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
2011-02-07 9:44 ` Thierry Volpiatto
2011-02-07 10:16 ` Eli Zaretskii
2011-02-07 12:10 ` Le Wang [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='AANLkTimP_6EyDYH=bYkRaraYivrMXC08SnWtHcOp=yV-@mail.gmail.com' \
--to=l26wang@gmail.com \
--cc=eliz@gnu.org \
--cc=help-gnu-emacs@gnu.org \
--cc=tassilo@member.fsf.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 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.