unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: npostavs@users.sourceforge.net
To: me@alandmoore.com
Cc: 25549@debbugs.gnu.org
Subject: bug#25549: 25.1; eshell grep gives inconsistent output
Date: Sun, 29 Jan 2017 12:25:48 -0500	[thread overview]
Message-ID: <874m0hsrqb.fsf@users.sourceforge.net> (raw)
In-Reply-To: <87tw8lzdaj.fsf@it-alanm.williamson-tn.org> (me@alandmoore.com's message of "Thu, 26 Jan 2017 16:06:44 -0600")

tags 25549 moreinfo unreproducible
quit

me@alandmoore.com writes:

> When using grep on a large file in eshell, the output is sometimes
>   inconsistent. For example, when grepping for a string in my
> server's apache2 access log (~5 MB) I got anywhere from around 200 to
> around 1300 results, just running the same grep command over and over
> (the file itself was not changing significantly).
>
> The bug cannot be consistently reproduced, but has happened in multiple
> situations and others have reportedly reproduced it per discussion on
> reddit
> (https://www.reddit.com/r/emacs/comments/5qbd70/trampeshellgrep_returning_wildly_different/).

Could you give some hints on what is needed to reproduce this?  Is it
the size of the grepped file?  Number of matches?  Are there some
non-ascii characters in the file?  Is Tramp required (the first post in
the linked thread mentions it, but some other comments seem to suggest
it's not required)?  You mention the file was not changing
"significantly", does this happen also when file stays *exactly*
identical?

I tried doubling up xdisp.c until it was over 5 MB, but grepping for "int"
in eshell returned a consistent number of matches.





  reply	other threads:[~2017-01-29 17:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-26 22:06 bug#25549: 25.1; eshell grep gives inconsistent output me
2017-01-29 17:25 ` npostavs [this message]
2017-01-30 15:29   ` me
2017-01-30 20:38 ` bug#25549: test case Tijs Mallaerts
2017-01-31  2:29   ` bug#25549: 25.1; eshell grep gives inconsistent output npostavs
2017-02-03  3:26     ` npostavs
2017-02-09  4:46       ` npostavs

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=874m0hsrqb.fsf@users.sourceforge.net \
    --to=npostavs@users.sourceforge.net \
    --cc=25549@debbugs.gnu.org \
    --cc=me@alandmoore.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.
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).