unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Andreas Schwab <schwab@linux-m68k.org>
To: Markus Triska <triska@metalevel.at>
Cc: 40375@debbugs.gnu.org, Noam Postavsky <npostavs@gmail.com>
Subject: bug#40375: 27.0.50; yank unexpectedly depends on progn
Date: Mon, 13 Apr 2020 18:35:01 +0200	[thread overview]
Message-ID: <87r1wrjqdm.fsf@igel.home> (raw)
In-Reply-To: <87o8sbgkig.fsf@metalevel.at> (Markus Triska's message of "Wed, 01 Apr 2020 19:53:43 +0200")

On Apr 01 2020, Markus Triska wrote:

> When I start Emacs with:
>
>     $ emacs -Q yank.el --eval='(eval-buffer)'
>
> and then press C-y to yank, the image that was most recently killed via
> kill-new is unexpectedly not inserted. However, when I invoke Emacs
> with the form wrapped in (progn ...), followed by (yank), i.e. with:
>
>     $ emacs -Q yank.el --eval='(progn (eval-buffer) (yank))'
>
> then the image is indeed inserted.

What does your interprogram-paste-function return?

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510  2552 DF73 E780 A9DA AEC1
"And now for something completely different."





  parent reply	other threads:[~2020-04-13 16:35 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-01 16:14 bug#40375: 27.0.50; yank unexpectedly depends on progn Markus Triska
2020-04-01 16:57 ` Noam Postavsky
2020-04-01 17:53   ` Markus Triska
2020-04-01 23:11     ` Noam Postavsky
2020-04-13 16:14       ` Noam Postavsky
2020-04-13 16:22         ` Markus Triska
2020-04-13 16:30           ` Noam Postavsky
2020-04-13 16:35     ` Andreas Schwab [this message]
2020-04-13 18:01       ` Markus Triska
2020-04-13 18:34         ` Eli Zaretskii
2020-04-13 18:52           ` Markus Triska
2020-04-13 19:35             ` Eli Zaretskii
2020-04-13 19:46               ` Markus Triska
2020-04-13 22:16                 ` Noam Postavsky
2020-04-13 22:44                   ` Drew Adams
2020-04-14  5:39                   ` 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=87r1wrjqdm.fsf@igel.home \
    --to=schwab@linux-m68k.org \
    --cc=40375@debbugs.gnu.org \
    --cc=npostavs@gmail.com \
    --cc=triska@metalevel.at \
    /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).