all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Kaushal Modi <kaushal.modi@gmail.com>
To: Emacs developers <emacs-devel@gnu.org>
Subject: Help figuring out origin of error: "ERROR in parse_header: buffer was .. client: reader got error Success"
Date: Wed, 23 Jan 2019 12:18:45 -0500	[thread overview]
Message-ID: <CAFyQvY0r=Gsy4a5qJ=bqyiSXzy2e_R2UXvpQz94ZByA60q_eKA@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1281 bytes --]

Hello,

I have ended up with an unusual regression scenario on emacs master, which
I can reproduce only with the combination of M-x shell-command-on-region
and the par[1] CLI utility.

I don't see the issue on emacs 26.1.

The issue is that when I select a region of text and do `M-| par`, I get
this error:

ERROR in parse_header: buffer was ';; This buffer is for te'
error: client: reader got error Success

I got that error by launching emacs -Q (master branch), selecting the text
in the scratch buffer and doing `M-| par`. Interestingly that error doesn't
happen on running `od', or `cat' or any other command via M-|.

I contacted the par author Adam Costello, and he had this to say:

> > I grepped Emacs source and par source and none contain any part of
> > that error string.

> Emacs versions earlier than 24 have a lib-src/fakemail.c that contains a
> parse_header() function.  Could that be involved?

But I don't know .. this is a very recent regression .. some time after
26.1 release.

I have already reported this bug at
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=34174. I am emailing in this
mailing list to see if anyone here can connect the dots between that error
and specifically using par.

Thoughts?


[1]: http://www.nicemice.net/par/

--
Kaushal Modi

[-- Attachment #2: Type: text/html, Size: 2022 bytes --]

                 reply	other threads:[~2019-01-23 17:18 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CAFyQvY0r=Gsy4a5qJ=bqyiSXzy2e_R2UXvpQz94ZByA60q_eKA@mail.gmail.com' \
    --to=kaushal.modi@gmail.com \
    --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 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.