GNU bug report logs -
#6532
text properties follow along text copied to other buffers
Previous Next
Reported by: jidanni <at> jidanni.org
Date: Mon, 28 Jun 2010 17:44:02 UTC
Severity: normal
Done: Eli Zaretskii <eliz <at> gnu.org>
Bug is archived. No further changes may be made.
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 6532 in the body.
You can then email your comments to 6532 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
owner <at> debbugs.gnu.org, bug-gnu-emacs <at> gnu.org
:
bug#6532
; Package
emacs
.
(Mon, 28 Jun 2010 17:44:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
jidanni <at> jidanni.org
:
New bug report received and forwarded. Copy sent to
bug-gnu-emacs <at> gnu.org
.
(Mon, 28 Jun 2010 17:44:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
Is it a bug or a feature that when I copy some glowing blue characters
to another buffer, they stay glowing blue, instead of adopting the drab
colors of other text that was typed into that buffer?
E.g., C-u C-x = shows this, even on text that was copied to a plain
text-mode buffer:
There are text properties here:
balloon-help nil
face (w3m-anchor w3m-italic w3m-bold)
rear-nonsticky t
w3m-anchor-sequence 23
w3m-balloon-help "http://www.youtube.com/watch?v=X9xWuvRaQ6g"
w3m-href-anchor "http://www.youtube.com/watch?v=X9xWuvRaQ6g"
w3m-name-anchor [Show]
w3m-name-anchor2 ("tsf-oq" "logo" "gbe" "gbf" "gbn")
w3m-safe-url-regexp nil
Indeed, the only way I know to clean them up is
C-x h C-u <escape> | c a t <return>
emacs-version "24.0.50.1"
Information forwarded
to
owner <at> debbugs.gnu.org, bug-gnu-emacs <at> gnu.org
:
bug#6532
; Package
emacs
.
(Mon, 28 Jun 2010 18:14:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 6532 <at> debbugs.gnu.org (full text, mbox):
> Is it a bug or a feature
A feature. And it's customizable (and bindable).
See `yank-excluded-properties'.
Information forwarded
to
owner <at> debbugs.gnu.org, bug-gnu-emacs <at> gnu.org
:
bug#6532
; Package
emacs
.
(Mon, 28 Jun 2010 18:19:02 GMT)
Full text and
rfc822 format available.
Message #11 received at 6532 <at> debbugs.gnu.org (full text, mbox):
>>>>> "A" == Drew Adams <drew.adams <at> oracle.com> writes:
>> Is it a bug or a feature
A> A feature. And it's customizable (and bindable).
A> See `yank-excluded-properties'.
OK, found it. Instead of the extra long list it comes with and is hard
to maintain I bet, I wonder why it isn't 't' to begin with. OK, thanks.
Information forwarded
to
owner <at> debbugs.gnu.org, bug-gnu-emacs <at> gnu.org
:
bug#6532
; Package
emacs
.
(Mon, 28 Jun 2010 18:29:02 GMT)
Full text and
rfc822 format available.
Message #14 received at 6532 <at> debbugs.gnu.org (full text, mbox):
jidanni <at> jidanni.org skrev 2010-06-28 19.42:
> Is it a bug or a feature that when I copy some glowing blue characters
> to another buffer, they stay glowing blue, instead of adopting the drab
> colors of other text that was typed into that buffer?
>
I think it is a feature, its been like that for a long time. Not that I like
it, copying from ediff-colored text or *compilation* to a text file looks
funny. C-x C-s, kill buffer and reopen the file is my workaround.
> Indeed, the only way I know to clean them up is
> C-x h C-u<escape> | c a t<return>
>
An idea is to have some popup that appears if text properties differs between
source and destination. It can ask if you want to adopt to source or
destination. I don't know how tricky that would be.
Jan D.
Information forwarded
to
owner <at> debbugs.gnu.org, bug-gnu-emacs <at> gnu.org
:
bug#6532
; Package
emacs
.
(Mon, 28 Jun 2010 18:35:02 GMT)
Full text and
rfc822 format available.
Message #17 received at 6532 <at> debbugs.gnu.org (full text, mbox):
> >> Is it a bug or a feature
>
> A> A feature. And it's customizable (and bindable).
> A> See `yank-excluded-properties'.
>
> OK, found it. Instead of the extra long list it comes with and is hard
> to maintain I bet, I wonder why it isn't 't' to begin with.
> OK, thanks.
The default value of the option needs to be the most reasonable value for most
uses by most people - or at least a reasonable value. ;-)
The value chosen seems like a pretty good choice, to me. What matters most to
me is that yanking does not exclude `face' but it does exclude `mouse-face'.
Whether most people want to yank with faces by default is questionable, but that
fits my use.
FWIW - One thing that might be helpful (it is present in some other editors)
would be an Edit menu item to paste without properties (or paste with some
preferred set of properties whenever no-property yanking is the user's default
behavior).
Information forwarded
to
owner <at> debbugs.gnu.org, bug-gnu-emacs <at> gnu.org
:
bug#6532
; Package
emacs
.
(Mon, 28 Jun 2010 18:41:02 GMT)
Full text and
rfc822 format available.
Message #20 received at 6532 <at> debbugs.gnu.org (full text, mbox):
>>>>> "JD" == Jan Djärv <jan.h.d <at> swipnet.se> writes:
JD> An idea is to have some popup that appears if text properties differs
JD> between source and destination. It can ask if you want to adopt to
JD> source or destination. I don't know how tricky that would be.
"Gee, all I wanted to do was copy text, now I'm getting popups".
Anyway, perhaps when copying from one message-mode buffer to another
message-mode buffer, keeping properties makes sense... but the rest of
the time not. So I'm making the default 't' for me. Anyways, does
copying back an forth from Firefox to emacs preserve properties? No. Did
I ever feel bad about it? No. If emacs were WYSIWYG like Word™ then
maybe it would make sense, otherwise not. However I think I'll be
stepping out of the conversation right about now...
Reply sent
to
Eli Zaretskii <eliz <at> gnu.org>
:
You have taken responsibility.
(Mon, 28 Jun 2010 18:41:02 GMT)
Full text and
rfc822 format available.
Notification sent
to
jidanni <at> jidanni.org
:
bug acknowledged by developer.
(Mon, 28 Jun 2010 18:41:02 GMT)
Full text and
rfc822 format available.
Message #25 received at 6532-done <at> debbugs.gnu.org (full text, mbox):
> From: jidanni <at> jidanni.org
> Date: Tue, 29 Jun 2010 01:42:57 +0800
> Cc:
>
> Is it a bug or a feature that when I copy some glowing blue characters
> to another buffer, they stay glowing blue, instead of adopting the drab
> colors of other text that was typed into that buffer?
Feature. If you don't like it, set yank-excluded-properties to t. Or
type "M-o M-o" after yanking.
Information forwarded
to
owner <at> debbugs.gnu.org, bug-gnu-emacs <at> gnu.org
:
bug#6532
; Package
emacs
.
(Mon, 28 Jun 2010 21:04:01 GMT)
Full text and
rfc822 format available.
Message #28 received at 6532 <at> debbugs.gnu.org (full text, mbox):
Nice, you learn something every day.
Jan D.
Eli Zaretskii skrev 2010-06-28 20.42:
>> From: jidanni <at> jidanni.org
>> Date: Tue, 29 Jun 2010 01:42:57 +0800
>> Cc:
>>
>> Is it a bug or a feature that when I copy some glowing blue characters
>> to another buffer, they stay glowing blue, instead of adopting the drab
>> colors of other text that was typed into that buffer?
>
> Feature. If you don't like it, set yank-excluded-properties to t. Or
> type "M-o M-o" after yanking.
>
>
Message #29 received at 6532-done <at> debbugs.gnu.org (full text, mbox):
> Feature. If you don't like it, set yank-excluded-properties to t. Or
> type "M-o M-o" after yanking.
Too bad that `M-o M-o' is undocumented. At least I cannot find it in the Emacs
manual. And I see nothing about it in the help for `yank' and its linked help,
including for `yank-excluded-properties'.
The doc should clarify more generally the relation between font-lock mode and
(yanking) text with properties. In particular, even with
`yank-excluded-properties' nil, users will not see text properties on text they
yank if they are in font-lock-mode.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Tue, 27 Jul 2010 11:24:03 GMT)
Full text and
rfc822 format available.
This bug report was last modified 15 years and 24 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.