emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[debbugs-tracker] bug#35075: closed ([26.1] reading a list of buffer obj


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#35075: closed ([26.1] reading a list of buffer objects from a file)
Date: Tue, 02 Apr 2019 11:06:02 +0000

Your message dated Tue, 02 Apr 2019 12:04:57 +0100
with message-id <address@hidden>
and subject line Re: bug#35075: [26.1] reading a list of buffer objects from a 
file
has caused the debbugs.gnu.org bug report #35075,
regarding [26.1] reading a list of buffer objects from a file
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
35075: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=35075
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: [26.1] reading a list of buffer objects from a file Date: Mon, 1 Apr 2019 20:02:04 -0400 User-agent: NeoMutt/20180716
In GNU Emacs 26.1 (build 2, x86_64-pc-linux-gnu, GTK+ Version 3.24.4) of
2019-02-03, modified by Debian:

When attempting to `read' a list that contains buffer objects, Emacs reports:

  Error while reading ~/test; Invalid read syntax: "#"



--
hkp://keys.gnupg.net
CA45 09B5 5351 7C11 A9D1  7286 0036 9E45 1595 8BC0



--- End Message ---
--- Begin Message --- Subject: Re: bug#35075: [26.1] reading a list of buffer objects from a file Date: Tue, 02 Apr 2019 12:04:57 +0100 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux)
tags 35075 notabug
quit

Boruch Baum <address@hidden> writes:

> Thanks for the referemce. If the only 'solution' then is to edit the
> list before saving, then I guess this report can be closed.
>
> On 2019-04-02 01:17, Basil L. Contovounesios wrote:
>> Boruch Baum <address@hidden> writes:
>>
>> > When attempting to `read' a list that contains buffer objects, Emacs 
>> > reports:
>> >
>> >   Error while reading ~/test; Invalid read syntax: "#"
>>
>> Buffer objects have no read syntax;
>> see (info "(elisp) Printed Representation").

I'm not sure what "editing" the list entails, or what you're trying to
achieve, but FWIW you can always print and read buffer names as strings.

In any case, I'm closing the bug report because the error you
encountered is expected and documented behaviour.

Thanks,

-- 
Basil


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]