unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Chen Zhaoyang <chenzhauyang@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: save-excursion not working for python-shell-send-buffer
Date: Tue, 14 Feb 2023 23:56:26 -0600	[thread overview]
Message-ID: <875yc3zd2t.fsf@gmail.com> (raw)

Hello,

After executing (python-shell-send-buffer) my point does not return to
the mark but the beginning of the buffer. I am able to reproduce this
behavior on "emacs -Q" (my emacs is "GNU Emacs 30.0.50 (build 11,
x86_64-pc-linux-gnu, GTK+ Version 3.24.24, cairo version 1.16.0) of
2023-02-14"). I wrote a wrapper function like this

(defun site/python-shell-send-buffer ()
  (interactive)
  (save-excursion
    (python-shell-send-buffer nil)))

which works as desired (??).

Best,
Chen Zhaoyang




             reply	other threads:[~2023-02-15  5:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-15  5:56 Chen Zhaoyang [this message]
2023-02-15 13:24 ` save-excursion not working for python-shell-send-buffer Eli Zaretskii
2023-02-15 14:23   ` Gregory Heytings
2023-02-15 16:16   ` Chen Zhaoyang

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=875yc3zd2t.fsf@gmail.com \
    --to=chenzhauyang@gmail.com \
    --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).