Bug 1006882 - emacs adds trailing whitespace in comments when copying from terminal
emacs adds trailing whitespace in comments when copying from terminal
Product: Fedora
Classification: Fedora
Component: emacs (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Petr Hracek
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2013-09-11 08:53 EDT by javiermon
Modified: 2015-02-17 12:08 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2015-02-17 12:08:45 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Example of .c file to test the bug (3.95 KB, text/x-csrc)
2013-09-11 08:53 EDT, javiermon
no flags Details

  None (edit)
Description javiermon 2013-09-11 08:53:27 EDT
Created attachment 796361 [details]
Example of .c file to test the bug

Description of problem:
When I select text from a source file with emacs-nox or emacs -nw if I select commented code the text selected includes non-existant trailing whitespace. This happens with various types of source code, I've tested with .c and lisp. Also, I tested with no .emacs file so this basically happens on a clean emacs installation.

Version-Release number of selected component (if applicable):
emacs 24.3 fc19 x86_64

How reproducible:

Steps to Reproduce:
1. start emacs -nw
2. open a .c file with comments
3. select lines that include comments, those lines are selected until the end of line. Lines without comment will only be selected until the last character (i.e. no trailing whitespace).

Actual results:

Expected results:
Lines with comments should only be copied as any other line, until the last character.

Additional info:
I think this has something to do with the way emacs does syntax highlighting, because if you rename the .c file to .c_old this bug doesn't appear.
Comment 1 javiermon 2014-06-17 08:05:38 EDT
I've found out this is happening when semantic mode is turned on.
Comment 2 javiermon 2014-06-17 08:10:13 EDT
I meant, that this also happens with semantic mode on all lines, not just comments. Sorry for the confusing comment.
Comment 3 Fedora End Of Life 2015-01-09 14:48:05 EST
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 4 Fedora End Of Life 2015-02-17 12:08:45 EST
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.