From: "Jacek Chrząszcz" <chrzaszcz@mimuw.edu.pl>
To: emacs-pretest-bug@gnu.org
Subject: longlines mode and kill-line: missing space between boundary words
Date: Tue, 4 Dec 2007 23:52:13 +0100 [thread overview]
Message-ID: <c12801b90712041452o14ace8bv680c15a1213ed5a@mail.gmail.com> (raw)
Please write in English if possible, because the Emacs maintainers
usually do not have translators to read other languages for them.
Your bug report will be posted to the emacs-pretest-bug@gnu.org mailing list.
Please describe exactly what actions triggered the bug
and the precise symptoms of the bug:
In longlines mode when I press C-k (i.e. a kill-line command) in a
long paragraph with soft linebreaks and then press C-y to yank the
killed line somewhere, the spaces between the words on soft-broken
lines' boundaries disapear.
For example: suppose the paragraph below has soft linebreaks (and not
hard) then when I put the cursor on the first line and press C-k C-y I
should get exactly the same paragraph.
Lazy fox jumped over crazy dogs Lazy fox jumped over crazy dogs Lazy
fox jumped over crazy dogs Lazy fox jumped over crazy dogs Lazy fox
jumped over crazy dogs Lazy fox jumped over crazy dogs Lazy fox jumped
over crazy dogs
And what I get is:
Lazy fox jumped over crazy dogs Lazy fox jumped over crazy dogs
Lazyfox jumped over crazy dogs Lazy fox jumped over crazy dogs Lazy
fox jumped over crazy dogs Lazy fox jumped over crazy dogs Lazy fox
jumped over crazy dogs
(with again soft-breaks at end of lines). Remark "Lazyfox" on the second line.
I guess after kill-line the longline mode automatically compresses the
soft-linebreak at the end of the line (because the space is
temporarily turned into a soft linebreak) and the information about
the space does not get into the kill ring.
The consistent behaviour would be either to add the missing space to
the kill ring or (it that is impossible or too hard) to kill the whole
paragraph at once (since it in fact is a single line). The first
behaviour clearly looks better to me.
Although I am using emacs 23 now (from
http://peadrop.com/blog/2007/01/06/pretty-emacs under Ubuntu 7.04), I
get the same behaviour in ubuntu-distributed emacs 21 as well.
Cheers,
Jacek
If Emacs crashed, and you have the Emacs process in the gdb debugger,
please include the output from the following gdb commands:
`bt full' and `xbacktrace'.
If you would like to further debug the crash, please read the file
/usr/share/emacs/23.0.0/etc/DEBUG for instructions.
In GNU Emacs 23.0.0.1 (i486-pc-linux-gnu, GTK+ Version 2.10.11)
of 2007-07-06 on helios
Windowing system distributor `The X.Org Foundation', version 11.0.70200000
configured using `configure '--build' 'i486-linux-gnu' '--host'
'i486-linux-gnu' '--prefix=/usr' '--sharedstatedir=/var/lib'
'--libexecdir=/usr/lib' '--localstatedir=/var'
'--infodir=/usr/share/info' '--mandir=/usr/share/man' '--with-pop=yes'
'--enable-locallisppath=/etc/emacs-snapshot:/etc/emacs:/usr/local/share/emacs/23.0.0/site-lisp:/usr/local/share/emacs/site-lisp:/usr/share/emacs/23.0.0/site-lisp:/usr/share/emacs/site-lisp:/usr/share/emacs/23.0.0/leim'
'--with-x=yes' '--with-x-toolkit=gtk' '--enable-font-backend'
'--with-xft' '--with-freetype' 'build_alias=i486-linux-gnu'
'host_alias=i486-linux-gnu' 'CC=gcc' 'CFLAGS=-DDEBIAN
-DSITELOAD_PURESIZE_EXTRA=5000 -g -O2''
Important settings:
value of $LC_ALL: nil
value of $LC_COLLATE: nil
value of $LC_CTYPE: nil
value of $LC_MESSAGES: nil
value of $LC_MONETARY: nil
value of $LC_NUMERIC: nil
value of $LC_TIME: nil
value of $LANG: pl_PL.UTF-8
value of $XMODIFIERS: nil
locale-coding-system: utf-8-unix
default-enable-multibyte-characters: t
Major mode: Text
Minor modes in effect:
longlines-mode: t
shell-dirtrack-mode: t
tooltip-mode: t
mouse-wheel-mode: t
use-hard-newlines: t
menu-bar-mode: t
file-name-shadow-mode: t
global-font-lock-mode: t
font-lock-mode: t
blink-cursor-mode: t
global-auto-composition-mode: t
auto-composition-mode: t
auto-compression-mode: t
line-number-mode: t
Recent input:
<down-mouse-1> <mouse-1> C-x C-f p l i k <tab> . <tab>
t x t <return> <down-mouse-2> <mouse-2> s M-x l o n
g <tab> <return> <up> <up> C-a <right> <right> <right>
<right> SPC <up> C-k C-y <help-echo> <help-echo> <help-echo>
<help-echo> <help-echo> <help-echo> <help-echo> <help-echo>
<help-echo> <help-echo> <help-echo> <help-echo> <menu-bar>
<help-menu> <report-emacs-bug>
Recent messages:
Loading /usr/share/emacs/23.0.0/lisp/longlines.el.gz...
Loading jka-compr...done
uncompressing longlines.el.gz...done
Loading easy-mmode...done
Loading /usr/share/emacs/23.0.0/lisp/longlines.el.gz...done
Longlines mode enabled
Mark set
Loading emacsbug...
Loading regexp-opt...done
Loading emacsbug...done
next reply other threads:[~2007-12-04 22:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-04 22:52 Jacek Chrząszcz [this message]
2007-12-05 22:58 ` longlines mode and kill-line: missing space between boundary words martin rudalics
2007-12-12 13:57 ` Kevin Rodgers
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=c12801b90712041452o14ace8bv680c15a1213ed5a@mail.gmail.com \
--to=chrzaszcz@mimuw.edu.pl \
--cc=emacs-pretest-bug@gnu.org \
/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).