From: "Jan Djärv" <jan.h.d@swipnet.se>
To: Angelo Graziosi <angelo.graziosi@alice.it>
Cc: 16382@debbugs.gnu.org
Subject: bug#16382: Cut/Copy tool-bar icons issue
Date: Tue, 14 Jan 2014 18:47:45 +0100 [thread overview]
Message-ID: <91321D5C-3AC5-4E50-AB37-4ACDAF8C16CB@swipnet.se> (raw)
In-Reply-To: <52D57326.6050305@alice.it>
Hello.
14 jan 2014 kl. 18:25 skrev Angelo Graziosi <angelo.graziosi@alice.it>:
> Il 14/01/2014 17.07, Jan Djärv ha scritto:
>> Hello.
>>
>> 14 jan 2014 kl. 10:03 skrev Angelo Graziosi <angelo.graziosi@alice.it>:
>>
>>> Should we open a new bug report for this?
>>>
>>
>> This report is fine. The omission to copy to PRIMARY looks intended, because when text is read-only and cut acts like copy, text is copied to PRIMARY.
>
> "intended" ? If it is intended, which is its usefulness?
>
> If one wants to move text from a place to another, this doesn't work using the mouse and the "cut" icon on the tool-bar...
>
> 1. select the text with mouse-1 (dragging over the text)
This should already put the text in PRIMARY.
> 2. click the "cut" icon on the tool-bar: the text is removed
> 3. now move the mouse pointer where you want the text to reappear
> 4. click mouse-2 to paste: nothing happens
>
> So, newly, which the usefulness of the above "intended" omission?
>
>
>> I wonder if there is some thought behind this we don't see.
>
> ah..
>
Does it work if you use C-w instead of cut?
Jan D.
next prev parent reply other threads:[~2014-01-14 17:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-07 14:07 bug#16382: Cut/Copy tool-bar icons issue Angelo Graziosi
2014-01-07 17:27 ` Jan Djärv
2014-01-09 2:00 ` Stefan Monnier
2014-01-12 11:26 ` Angelo Graziosi
2014-01-12 18:03 ` Jan Djärv
2014-01-14 9:03 ` Angelo Graziosi
2014-01-14 16:07 ` Jan Djärv
2014-01-14 17:25 ` Angelo Graziosi
2014-01-14 17:47 ` Jan Djärv [this message]
2014-01-14 17:54 ` Angelo Graziosi
2014-01-14 17:59 ` Jan Djärv
2014-01-18 15:13 ` Jan Djärv
2014-01-18 16:19 ` Angelo Graziosi
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=91321D5C-3AC5-4E50-AB37-4ACDAF8C16CB@swipnet.se \
--to=jan.h.d@swipnet.se \
--cc=16382@debbugs.gnu.org \
--cc=angelo.graziosi@alice.it \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.