From: Barry Margolin <barmar@alum.mit.edu>
To: help-gnu-emacs@gnu.org
Subject: Re: thing-at-point: inconsistent behaviour?
Date: Thu, 16 Aug 2012 19:19:06 -0400 [thread overview]
Message-ID: <barmar-8A9F97.19190616082012@news.eternal-september.org> (raw)
In-Reply-To: a94o01FiegU1@mid.individual.net
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 727 bytes --]
In article <a94o01FiegU1@mid.individual.net>,
Raffaele Ricciardi <rfflrccrd@gmail.com> wrote:
> On 08/16/2012 05:24 PM, Andreas Röhler wrote:
> > Not to expect is changing the computers internal state already when
> > picking an object by thing-at-point.
> > That's what is done by "intern" however.
>
> Indeed this is an undesirable side effect of `symbol-at-point' calling
> `intern'. Could `intern' be replaced with `make-symbol'?
Most applications that use symbols need interned symbols. If you're
doing something that wants an uninterned symbol, call (make-symbol
(thing-at-point 'symbol)).
--
Barry Margolin, barmar@alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***
next prev parent reply other threads:[~2012-08-16 23:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-15 18:08 thing-at-point: inconsistent behaviour? Raffaele Ricciardi
2012-08-15 18:34 ` Barry Margolin
2012-08-15 18:44 ` Drew Adams
2012-08-15 19:00 ` Raffaele Ricciardi
2012-08-16 11:52 ` Andreas Röhler
[not found] ` <mailman.7107.1345117968.855.help-gnu-emacs@gnu.org>
2012-08-16 15:48 ` Barry Margolin
2012-08-16 16:24 ` Andreas Röhler
[not found] ` <mailman.7114.1345134264.855.help-gnu-emacs@gnu.org>
2012-08-16 17:12 ` Raffaele Ricciardi
2012-08-16 23:19 ` Barry Margolin [this message]
2012-08-17 0:46 ` Drew Adams
[not found] ` <mailman.7128.1345164390.855.help-gnu-emacs@gnu.org>
2012-08-17 1:46 ` Barry Margolin
2012-08-17 4:38 ` Drew Adams
[not found] ` <mailman.7135.1345178331.855.help-gnu-emacs@gnu.org>
2012-08-17 9:23 ` Raffaele Ricciardi
2012-08-20 0:15 ` Drew Adams
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=barmar-8A9F97.19190616082012@news.eternal-september.org \
--to=barmar@alum.mit.edu \
--cc=help-gnu-emacs@gnu.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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).