From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Peter Milliken Newsgroups: gmane.emacs.bugs Subject: bug#33441: reading and printing Lisp Objects - what changed from 25.3.1 to 26.1? Date: Wed, 21 Nov 2018 15:21:43 +1100 Message-ID: References: <837eh7hz33.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="000000000000057722057b2517b6" X-Trace: blaine.gmane.org 1542774007 30150 195.159.176.226 (21 Nov 2018 04:20:07 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Wed, 21 Nov 2018 04:20:07 +0000 (UTC) Cc: 33441@debbugs.gnu.org, eggert@cs.ucla.edu, npostavs@gmail.com To: eliz@gnu.org Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Wed Nov 21 05:20:02 2018 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1gPJzd-0007ec-Vh for geb-bug-gnu-emacs@m.gmane.org; Wed, 21 Nov 2018 05:20:02 +0100 Original-Received: from localhost ([::1]:37130 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gPK1k-0000LN-BN for geb-bug-gnu-emacs@m.gmane.org; Tue, 20 Nov 2018 23:22:12 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:56961) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gPK1d-0000KI-Jb for bug-gnu-emacs@gnu.org; Tue, 20 Nov 2018 23:22:06 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gPK1a-0003vL-F6 for bug-gnu-emacs@gnu.org; Tue, 20 Nov 2018 23:22:05 -0500 Original-Received: from debbugs.gnu.org ([208.118.235.43]:33409) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gPK1a-0003vF-CK for bug-gnu-emacs@gnu.org; Tue, 20 Nov 2018 23:22:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1gPK1a-0002er-76 for bug-gnu-emacs@gnu.org; Tue, 20 Nov 2018 23:22:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Peter Milliken Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 21 Nov 2018 04:22:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 33441 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 33441-submit@debbugs.gnu.org id=B33441.154277412110205 (code B ref 33441); Wed, 21 Nov 2018 04:22:02 +0000 Original-Received: (at 33441) by debbugs.gnu.org; 21 Nov 2018 04:22:01 +0000 Original-Received: from localhost ([127.0.0.1]:37665 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1gPK1Y-0002eP-TO for submit@debbugs.gnu.org; Tue, 20 Nov 2018 23:22:01 -0500 Original-Received: from mail-io1-f45.google.com ([209.85.166.45]:37311) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1gPK1X-0002eA-GZ for 33441@debbugs.gnu.org; Tue, 20 Nov 2018 23:21:59 -0500 Original-Received: by mail-io1-f45.google.com with SMTP id a3so3100446ioc.4 for <33441@debbugs.gnu.org>; Tue, 20 Nov 2018 20:21:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=eqNfbnIZowJKFw+IFnOMe+6gdr7diI2ttplluI58vhQ=; b=npnu9LbUzY1StxhrZAqgGI/RwsWh1CCFq9jd5XuJG5UK7kkUjM/jd5p538g45dgfF2 4PrRW2mPnN1Ptc9jjUqALQrFkSD/ZEuI30RLNIswb6Pc+SGNGFPmuoeoruRhQQeQJNZC G+28KZVER7kL/H5U+3K/KwbW+SqCewVVfF2OSxfJrvftCRj0uUXK7NDvlTy/K0fTaWmq 3khP10/LYrN46D02xbg1FikG4JHWrjOPj7R5qIL1qB6iHgHUZSZ4O8qoWBIB2Ziisp94 OIY5uZf+L4o2cxJsmeEEdUSPD+nKVOhbtZfeNezEtrYJxw5NTeezccUgvoNTyWanKBl3 ZSDA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=eqNfbnIZowJKFw+IFnOMe+6gdr7diI2ttplluI58vhQ=; b=pWavh/iGW50VHKPTsDsiNVkWnceoDA1aCn07CkZgKOT2SPjIB/k6Ncdroh0GLIIgXj ykLkWcrJ0mykPqlFXPwCXMB48bHXWyfYml2lh0aX1/QOe+ysTyT11qYL2wzVnZktIr3C f+tGM63ydsCluRSHgxNesxQW+j2W6xMckgn9rRvE1BdJrZSp0jVPWeNES0QkY8DtU5Vo 7RFXY1qANpaWMFnZfVltsG1ScoygiJj7wHSwx2sh9B+q+61WiYDX3ibj3tMRGs4Xy657 RcxhTLpCA8SiCQrPFbkgz5B5noS3vvHOjMsswXGQdQdOr+iq4CF8de5fsjj+M0BX3Nji x8pg== X-Gm-Message-State: AA+aEWbP7M4mvFoHwSrxa7b2oDdA3uu7ozeLWku0p4lMKVJqftoJgQAI ye5fRpp//bhQtWI75MGj6//+n/lIXOgzflaM5L8= X-Google-Smtp-Source: AFSGD/UzKg6w/ZgIwmN/PlIRCtvPODLnGiDABGq9XILz7Bjvm+P2X+3YiFe0EPRHJsuN7l3VSH8nIGynYHtB8JPwwQo= X-Received: by 2002:a6b:f611:: with SMTP id n17-v6mr3097894ioh.99.1542774113792; Tue, 20 Nov 2018 20:21:53 -0800 (PST) In-Reply-To: <837eh7hz33.fsf@gnu.org> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:152615 Archived-At: --000000000000057722057b2517b6 Content-Type: text/plain; charset="UTF-8" I'm not sure that I am giving up on Emacs maintenance - the reference Noam supplied indicates this is a "well known" issue and somebody, has some intention, at some stage, to do something about it, but given the last update to referenced bug/email stream was 268 days ago, that intention may be on the back burner :-) Faking up a code snippet is not necessarily that easy - and, again, the problem described in 29220 sounds exactly like the issue I am having. I have already supplied the GitHub reference to my package and indicated the file that contains the functions that use/invoke the read/print processes. This is a working package, so, in my opinion, that satisfies that request :-) Using the package is not difficult, it is fully documented with its own user manual and the writing/reading process of the Lisp Objects is completely transparent to the user and happens automatically the first time the minor mode is invoked i.e. any maintainer investigating the issue shouldn't need to spend too much time getting to a point where they can debug the issue. The file(s) are written to the "user-emacs-directory". regards Peter On Wed, Nov 21, 2018 at 2:46 PM Eli Zaretskii wrote: > > From: Peter Milliken > > Date: Wed, 21 Nov 2018 12:52:57 +1100 > > Cc: 33441@debbugs.gnu.org, eggert@cs.ucla.edu > > > > I think perhaps you might want to put more information/warnings in > section 19 of the Elisp manual because it > > is obviously not true anymore that you can simply Print/Read any > arbitrary Lisp Object. > > > > I'm going to trap the error in my extension and just force > reading/"compiling" from the original text file instead > > of reading from the intermediate file created by the print process. This > will just cause a small delay to the user > > the first time that a set of language templates get loaded in an edit > session - probably not a big deal. Certainly, > > it is better than telling people my extension is "broken" and won't work > with 26.1 and onwards. > > I'd urge you not to give up on Emacs maintenance so quickly, and > provide the reproducer requested by Paul. Please give us a chance to > analyze the problem you are having and consider whether and how it > could or should be fixed. Leaving the problems unfixed because we > failed to look into them is not a good paradigm in maintaining such a > flexible and powerful software package as Emacs is. > > Thanks in advance. > --000000000000057722057b2517b6 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I'm not sure that I am giving up on Emacs mainten= ance - the reference Noam supplied indicates this is a "well known&quo= t; issue and somebody, has some intention, at some stage, to do something a= bout it, but given the last update to referenced bug/email stream was 268 d= ays ago, that intention may be on the back burner :-)=C2=A0

<= /div>Faking up a code snippet is not necessarily that easy - and, again, th= e problem described in 29220 sounds exactly like the issue I am having. I h= ave already supplied the GitHub reference to my package and indicated the f= ile that contains the functions that use/invoke the read/print processes. T= his is a working package, so, in my opinion, that satisfies that request :-= ) Using the package is not difficult, it is fully documented with its own u= ser manual and the writing/reading process of the Lisp Objects is completel= y transparent to the user and happens automatically the first time the mino= r mode is invoked i.e. any maintainer investigating the issue shouldn't= need to spend too much time getting to a point where they can debug the is= sue. The file(s) are written to the "user-emacs-directory".
<= br>
regards
Peter


=

On Wed, Nov 21, 2018 at 2:46 PM Eli Zaretskii <eliz@gnu.org> wrote:
> From: Peter Milliken <peter.milliken@gmail.com>
> Date: Wed, 21 Nov 2018 12:52:57 +1100
> Cc: 33441@d= ebbugs.gnu.org, eggert@cs.ucla.edu
>
> I think perhaps you might want to put more information/warnings in sec= tion 19 of the Elisp manual because it
> is obviously not true anymore that you can simply Print/Read any arbit= rary Lisp Object.
>
> I'm going to trap the error in my extension and just force reading= /"compiling" from the original text file instead
> of reading from the intermediate file created by the print process. Th= is will just cause a small delay to the user
> the first time that a set of language templates get loaded in an edit = session - probably not a big deal. Certainly,
> it is better than telling people my extension is "broken" an= d won't work with 26.1 and onwards.

I'd urge you not to give up on Emacs maintenance so quickly, and
provide the reproducer requested by Paul.=C2=A0 Please give us a chance to<= br> analyze the problem you are having and consider whether and how it
could or should be fixed.=C2=A0 Leaving the problems unfixed because we
failed to look into them is not a good paradigm in maintaining such a
flexible and powerful software package as Emacs is.

Thanks in advance.
--000000000000057722057b2517b6--