Gnus development mailing list
 help / color / mirror / Atom feed
From: Eze Ogwuma <typhoon@dircon.co.uk>
Subject: Re: Bad .newsrc.eld created by Gnus
Date: 09 Feb 1998 18:57:11 +0000	[thread overview]
Message-ID: <m3sopsehdk.fsf@localhost.localdomain> (raw)
In-Reply-To: Kurt Swanson's message of "09 Feb 1998 10:53:57 +0100"

Kurt Swanson <ksw@dna.lth.se> writes:

> Per Abrahamsen <abraham@dina.kvl.dk> writes:
> > SL Baur <steve@xemacs.org> writes:
> 
> > > Eze Ogwuma <typhoon@dircon.co.uk> writes:
> 
> > > > This is part of my file. It is the only part that contains "#".
> 
> 
> > > > (#("nntp+news.dircon.co.uk:comp.lang.java.help" 0 23 nil 23 42
> > >  ...
> > > > (#("nntp+news.dircon.co.uk:comp.lang.java.programmer" 0 23 nil 23 48
> 
> > > Who put in the #'s?  That's not valid Emacs or XEmacs.
> 
> > It look like Emacs print syntax for strings containing text properties.
> 
> > They usually occur when someone calls `buffer-substring' instead of
> > `buffer-substring-no-properties'.
> 
> There's also the posibility it is a symbol denoting that the next
> entity is a function, but I see this as less probable.


Hrvoje Niksic <hniksic@srce.hr> writes:

> That looks like the FSFmacs crockish syntax for strings with text
> properties.  Try this:
> 
> (let ((a "somestring"))
>   (put-text-property 0 5 'foo 'bar a)
>   a)
>   => "somestring"				; XEmacs
> 
>   => #("somestring" 0 5 (foo bar) 5 10 nil)	; FSFmacs
> 
> Familiar?  In FSF Emacs text properties change the printed
> representation of strings, and strings with properties might have
> leaked to `.newsrc.eld', somehow.
> 
> This matter is even more confusing because given that Common Lisp uses
> #(...)  syntax for vectors.

Hi,

Does anyone have some suggestions on how to proceed?

-- 
Eze Ogwuma


  parent reply	other threads:[~1998-02-09 18:57 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-02-03 18:37 Eze Ogwuma
1998-02-04 15:15 ` Simon Josefsson
1998-02-04 17:42   ` Eze Ogwuma
1998-02-04 19:13     ` Bud Rogers
1998-02-04 19:22       ` Eze Ogwuma
1998-02-04 17:54   ` Eze Ogwuma
1998-02-04 18:35     ` David S. Goldberg
1998-02-04 19:25       ` Eze Ogwuma
1998-02-04 19:01     ` Simon Josefsson
1998-02-04 19:44       ` Eze Ogwuma
1998-02-08 15:57         ` Lars Magne Ingebrigtsen
1998-02-08 16:59           ` Eze Ogwuma
1998-02-08 17:23             ` Lars Magne Ingebrigtsen
1998-02-08 19:17               ` Eze Ogwuma
1998-02-08 20:00                 ` Lars Magne Ingebrigtsen
1998-02-08 21:31                   ` Eze Ogwuma
1998-02-09  0:29                     ` SL Baur
1998-02-09  0:50                       ` Eze Ogwuma
1998-02-09  1:28                         ` SL Baur
1998-02-09  1:49                           ` Eze Ogwuma
1998-02-09  2:02                             ` SL Baur
1998-02-09  2:47                               ` Eze Ogwuma
1998-02-09  8:18                       ` Hrvoje Niksic
1998-02-09  9:47                       ` Per Abrahamsen
     [not found]                         ` <6fk9b5kssq.fsf@bavur.dna.lth.se>
1998-02-09 18:57                           ` Eze Ogwuma [this message]
1998-02-09 20:10                             ` Lars Magne Ingebrigtsen
1998-02-09 20:56                               ` Eze Ogwuma

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=m3sopsehdk.fsf@localhost.localdomain \
    --to=typhoon@dircon.co.uk \
    /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.
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 NNTP newsgroup(s).