all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Oleh Krehel <o.krehel@tue.nl>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: emacs-devel@gnu.org
Subject: Re: prin1-to-string noescape parameter
Date: Sat, 1 Nov 2014 09:28:54 +0100	[thread overview]
Message-ID: <CAJ1SQWBjfC34jc2+EMt+JK5WB9Lw9Ec2RmUOkhttOVOUio=WXQ@mail.gmail.com> (raw)
In-Reply-To: <87y4rvml0f.fsf@igel.home>

>>>> The issue is that if I have `foo.bar` in the code, and then I re-format
>>>> my code by:
>>>>
>>>> - read text
>>>> - delete text
>>>> - manipulate lisp object
>>>> - insert manipulated lisp object
>>>>
>>>> And now my code contains `foo\.bar`, although I don't want it.
>>>
>>> By passing the text through the lisp reading you are discarding all
>>> redundancy, so it is impossible in general to get back the original
>>> representation.
>>
>> Not possible in general, but the thing that I want can be done
>> by changing slightly the condition at line 240 of print.c
>
> No, you can't.  You have already discarded all necessary information.

Of course it's possible.
Since `foo.bar' and `foo\.bar' is the same symbol, why not
print it as "foo.bar" always? It looks better like this
in the source code anyway, and the reader has no problem with it.

regards,
Oleh



  reply	other threads:[~2014-11-01  8:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-31 16:15 prin1-to-string noescape parameter Oleh Krehel
2014-10-31 19:11 ` Andreas Schwab
2014-10-31 20:11   ` Oleh Krehel
2014-10-31 20:51     ` Andreas Schwab
2014-10-31 21:24       ` Oleh Krehel
2014-11-01  7:34         ` Andreas Schwab
2014-11-01  8:28           ` Oleh Krehel [this message]
2014-11-01 10:03             ` Andreas Schwab
2014-10-31 19:54 ` Stefan Monnier

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='CAJ1SQWBjfC34jc2+EMt+JK5WB9Lw9Ec2RmUOkhttOVOUio=WXQ@mail.gmail.com' \
    --to=o.krehel@tue.nl \
    --cc=emacs-devel@gnu.org \
    --cc=schwab@linux-m68k.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.