From: Toni Drabik <tdrabik@public.srce.hr>
Subject: Multipage articles bug
Date: 11 Sep 1999 15:26:28 +0200 [thread overview]
Message-ID: <7t1d7vptw8r.fsf@fly.srk.fer.hr> (raw)
Hi,
In articles with page breaks (i.e. ``embedded'' `C-l' characters),
click on ``Next page'' ends with an error. When I set
`debug-on-error' to `t', following backtrace is produced:
Signaling: (error "No selection or cut buffer available")
signal(error ("No selection or cut buffer available"))
cerror("No selection or cut buffer available")
apply(cerror "No selection or cut buffer available")
error("No selection or cut buffer available")
x-insert-selection(t)
x-yank-function()
mouse-consolidated-yank()
mouse-yank(#<buttondown-event button2>)
call-interactively(mouse-yank)
Pressing SPC to read next page still works, though... I'm using
Pterodactyl Gnus 0.96 on XEmacs 20.4.
--
Toni Drabik <tdrabik@public.srce.hr>
Warning: This article may be fatal if swallowed.
next reply other threads:[~1999-09-11 13:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-11 13:26 Toni Drabik [this message]
1999-09-25 9:01 ` Lars Magne Ingebrigtsen
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=7t1d7vptw8r.fsf@fly.srk.fer.hr \
--to=tdrabik@public.srce.hr \
/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 NNTP newsgroup(s).