unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Elias Mårtenson" <lokedhs@gmail.com>
To: Noam Postavsky <npostavs@users.sourceforge.net>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: goto-char doesn't stick
Date: Wed, 14 Jun 2017 18:30:53 +0800	[thread overview]
Message-ID: <CADtN0WLdqZ+dT6ywRt2UX5sscO6TWDJVir=ciMwZDs6S92tOQQ@mail.gmail.com> (raw)
In-Reply-To: <CAM-tV-_jWC7WVnCiG-3h-Nn6QwVVjh6OOF92wgSxAV+f=bPK8w@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 882 bytes --]

On 14 June 2017 at 18:26, Noam Postavsky <npostavs@users.sourceforge.net>
wrote:

> On Wed, Jun 14, 2017 at 5:45 AM, Elias Mårtenson <lokedhs@gmail.com>
> wrote:
> >
> >     (progn
> >       (set-buffer "z")
> >       (goto-char LOCATION))
> >
> > When I do this, point doesn't move. Or rather, it does move, but after
> the
> > conclusion of the ‘progn’ form, the cursor returns to its original
> location.
>
> Is the buffer "z" visible? You probably need to set-window-point too.
>

The same behaviour is seen regardless of whether the buffer is visible or
not.

It's easy to reproduce:

Just create a buffer "z", fill it with some text and place point in a
random position. Then open ‘ielm’ and type:

    (progn (set-buffer "z") (goto-char (point-min)))

Then switch to buffer "z" and observe that point is still in its original
position.

[-- Attachment #2: Type: text/html, Size: 1622 bytes --]

  reply	other threads:[~2017-06-14 10:30 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-14  9:45 goto-char doesn't stick Elias Mårtenson
2017-06-14  9:48 ` Andreas Schwab
2017-06-14 10:02   ` Elias Mårtenson
2017-06-14 10:29     ` Andreas Schwab
2017-06-14 10:32       ` Elias Mårtenson
2017-06-14 11:01         ` Yuri Khan
     [not found]           ` <CADtN0WJdwdFhTL2_=ZQbADKT0p+PKCJKfkjqt7hNdQduq5bmCQ@mail.gmail.com>
2017-06-14 11:09             ` Elias Mårtenson
2017-06-14 10:22 ` Peder O. Klingenberg
2017-06-14 10:26 ` Noam Postavsky
2017-06-14 10:30   ` Elias Mårtenson [this message]
2017-06-14 11:13 ` Eli Zaretskii
2017-06-14 11:16   ` Elias Mårtenson
2017-06-14 14:33     ` Eli Zaretskii
2017-06-14 14:59       ` Elias Mårtenson
2017-06-14 15:28         ` Eli Zaretskii
2017-06-15  3:53         ` Alex
2017-06-14 14:05   ` Drew Adams
2017-06-14 14:53     ` Eli Zaretskii
2017-06-15  6:59   ` Stefan Monnier
2017-06-15 11:37     ` Noam Postavsky
2017-06-15 12:55       ` martin rudalics
2017-06-15 13:24       ` Stefan Monnier
2017-06-15 14:30         ` Eli Zaretskii
2017-06-15 17:11           ` Stefan Monnier
2017-06-15 18:25             ` Eli Zaretskii
2017-06-15 19:10               ` Elias Mårtenson
2017-06-15 19:25                 ` Eli Zaretskii
2017-06-15 22:51               ` martin rudalics
2017-06-16  2:00                 ` Stefan Monnier
2017-06-15 14:32       ` Eli Zaretskii

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='CADtN0WLdqZ+dT6ywRt2UX5sscO6TWDJVir=ciMwZDs6S92tOQQ@mail.gmail.com' \
    --to=lokedhs@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=npostavs@users.sourceforge.net \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).