From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Kaushal Modi Newsgroups: gmane.emacs.devel 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 Message-ID: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="0000000000008433600580234b9d" Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="3540"; mail-complaints-to="usenet@blaine.gmane.org" To: Emacs developers Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Jan 23 18:20:29 2019 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gmMCS-0000oL-RC for ged-emacs-devel@m.gmane.org; Wed, 23 Jan 2019 18:20:28 +0100 Original-Received: from localhost ([127.0.0.1]:38880 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gmMCR-0006iU-Oc for ged-emacs-devel@m.gmane.org; Wed, 23 Jan 2019 12:20:27 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:39035) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gmMBa-0006i7-22 for emacs-devel@gnu.org; Wed, 23 Jan 2019 12:19:35 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gmMBW-0005RJ-8T for emacs-devel@gnu.org; Wed, 23 Jan 2019 12:19:33 -0500 Original-Received: from mail-lj1-x22d.google.com ([2a00:1450:4864:20::22d]:41123) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gmMBV-0005Oa-P5 for emacs-devel@gnu.org; Wed, 23 Jan 2019 12:19:30 -0500 Original-Received: by mail-lj1-x22d.google.com with SMTP id k15-v6so2631482ljc.8 for ; Wed, 23 Jan 2019 09:19:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=TJUYzR2eHOZQ2My4grAHpfhxcvxUd6UQVdt+9Kjp+y4=; b=sdXbciMQaZWsfz03rY8GCIhsUM+MDsh3yhossYVB5b7CtAXE+40oVuormcec1Xqsd5 KtEZ1ixQM1vgIavODICFKrkzKRp9d/9EEg1L/+ROQSU/6FdbbzGcRnr25BAEEjADoJgA QNE3AqvWKLFxfK0g5wywi41Vii/oEvw/Ko42OeQDa2stUHBIDCtSdZh44ZobtsFxtjUC 2KbvjK6em/55b5W0M/SZZZ43DFif4n4yYN00almmCM0+sKJj5odm6ACYB9MGFhMJwTY3 0ARNC6JvHcemZSruShUHiz3bUBaDPhrIwkbPRyu69rulI1JQxWB7Z9U+1DpcX7jqO5op zNfw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=TJUYzR2eHOZQ2My4grAHpfhxcvxUd6UQVdt+9Kjp+y4=; b=Wl5Yovvv4Ww6Vns7rxwRxZhTMMuD29VxYs40f/hq1+oZBi5J8vnyqMR2qrfFb7vUVu xqGdNHaa+I9GNFwtBXS1euAm3FyXJkHsXRGGaw9V+JAsTVlCJXouPZy1LxL61KKx7Zk/ IN0RqehNPhWpXXAQE2hNs8KT1pJDDEAJIbINEOLUNhKqFOB8f6/45iRy8BOxSA6hy0EU Li/4VnS3WLZHRPcp74ypikzcqDKG4O3eQ39aF3L1W9eod+Wk2GcvK4kJtHnvoXtinR4E FiMzdNk0Z0lqo8zvAvBjtwlTzof4ttpBj0RDFYH2vV59kRhiNphRFpvAKr1JEuv/xwhA /Mhg== X-Gm-Message-State: AJcUukckE+oVybed85keGB60czE4vRXHsbOHiDOhd+Zbn/1TZc2+ACq/ cTWaRU5qKBIRHwxzUg2ThgpCeT4Gzyzbk7gm3dz/fU2G X-Google-Smtp-Source: ALg8bN74djxu74NC+lztB3aMfWjxcn0Q6BafsCFUbsVfFHkK79wKarZ/N6bTc/H1XowFcC4ry6XHH37t67Bjje2u2eA= X-Received: by 2002:a2e:2c02:: with SMTP id s2-v6mr2573953ljs.118.1548263962716; Wed, 23 Jan 2019 09:19:22 -0800 (PST) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2a00:1450:4864:20::22d X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:232647 Archived-At: --0000000000008433600580234b9d Content-Type: text/plain; charset="UTF-8" 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 --0000000000008433600580234b9d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
He= llo,

I have ended up with an unusual regression sc= enario 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 ';; T= his buffer is for te'
error: client: reader got error Success

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

I contacted the par au= thor Adam Costello, and he had this to say:

=
> > I grepped Emacs source and par source an= d 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.=C2=A0 Could that be involved?

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

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

Thoughts?


<= div>

--
K= aushal Modi
--0000000000008433600580234b9d--