From: Kaushal Modi <kaushal.modi@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 29664@debbugs.gnu.org
Subject: bug#29664: 26.0.90; Auto Hscroll Mode + Visual Line Mode + Truncate don't work well together
Date: Mon, 11 Dec 2017 21:07:50 +0000 [thread overview]
Message-ID: <CAFyQvY1jfDF-FLkKzH4u5chzOp0MJmBX4FPMTBPrNcz838V00g@mail.gmail.com> (raw)
In-Reply-To: <83fu8hrnjn.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1724 bytes --]
On Mon, Dec 11, 2017 at 3:57 PM Eli Zaretskii <eliz@gnu.org> wrote:
>
> Why are you turning on both visual-line-mode and truncate-lines?
> These are mutually exclusive: the former is for wrapping long
> continued lines, the latter is for not continuing lines at all.
>
> What am I missing?
>
Yes, I understand that. But they were both enabled by mistake.
- The visual line mode was enabled by default in org-mode-hook
- And I happened to have "# eval: (toggle-truncate-lines 1)" in the Local
Variables footer in one of the Org files.
There were no signs of problem until C-a and C-e started misbehaving that
way.
Should emacs do the "right thing" and auto-disable the other if one got
enabled, or throw a warning?
This problem with C-a and C-e does not happen if skip this part in the test
setup:
(setq auto-hscroll-mode 'current-line)
- C-a works perfectly
- C-e does not jump instantly to the EOL, but progressively goes to the EOL
on hitting C-e, and eventually gets there (interesting behavior).
So at least with the default value of auto-hscroll-mode, a user is not
stuck wondering why C-a/C-e stopped working, even if they enabled
visual-line-mode and toggle-truncate-lines simultaneously by mistake.
PS: I noticed that the email client or the debbugs server auto-inserted
newlines in my test function.. I intend that insert form to insert a string
without any inbetween newlines.. like this:
(insert (concat "\n\ndlkasdjf lkdkmnf kd aksdjkldj laksdjflkasdf "
"aldksflakdjf alksdjldf lksdfjldkj lkjdfad "
"falksdflj asldkfjlasdf fjlaksdjflkj asdf "
"lasdkfalkds alsdfkj sdf lsdkfj sldkfjlksdjf "
"asldkfjlksdjfowieur nxc"))
--
Kaushal Modi
[-- Attachment #2: Type: text/html, Size: 2506 bytes --]
next prev parent reply other threads:[~2017-12-11 21:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-11 20:22 bug#29664: 26.0.90; Auto Hscroll Mode + Visual Line Mode + Truncate don't work well together Kaushal Modi
2017-12-11 20:56 ` Eli Zaretskii
2017-12-11 21:07 ` Kaushal Modi [this message]
2017-12-12 3:30 ` Eli Zaretskii
2017-12-12 8:02 ` Noam Postavsky
2021-09-03 6:36 ` Lars Ingebrigtsen
2021-09-03 7:06 ` Eli Zaretskii
2021-09-03 7:12 ` Lars Ingebrigtsen
2021-09-03 7:23 ` Eli Zaretskii
2021-09-03 10:47 ` Eli Zaretskii
2021-09-04 6:41 ` Lars Ingebrigtsen
2021-09-04 10:38 ` Eli Zaretskii
2021-09-03 7:57 ` Juri Linkov
2021-09-03 8:16 ` Lars 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
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=CAFyQvY1jfDF-FLkKzH4u5chzOp0MJmBX4FPMTBPrNcz838V00g@mail.gmail.com \
--to=kaushal.modi@gmail.com \
--cc=29664@debbugs.gnu.org \
--cc=eliz@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).