From: "N. Jackson" <nljlistbox2@gmail.com>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] Off-by-one error in width of Agenda window? [9.5.2 (release_9.5.2-25-gaf6f12 @ /data/installs/snapshots/emacs-28.1/lisp/org/)]
Date: Mon, 18 Apr 2022 15:06:49 -0400 [thread overview]
Message-ID: <87o80yqkhi.fsf@moondust.localdomain> (raw)
In-Reply-To: <87ee1ubje8.fsf@localhost> (Ihor Radchenko's message of "Mon, 18 Apr 2022 21:39:27 +0800")
At 21:39 +0800 on Monday 2022-04-18, Ihor Radchenko wrote:
> "N. Jackson" <nljlistbox2@gmail.com> writes:
>
>> Recently it seems as if Org Agenda thinks its window is one
>> character wider than it actually is. The incorrect behaviour I
>> observe is:
>
> I do not see any issues on both stable bugfix and main branches.
>
> Are you able to reproduce starting from emacs -Q?
No, it doesn't happen just with emacs -Q.
I have bisected my init file and narrowed it down to this setting in
my custom-set-variables:
'(fringe-mode '(nil . 0) nil (fringe))
Here is a recipe to reproduce the problem from emacs -Q:
0. M-x global-visual-line-mode RET
1. M-x org-agenda RET n [To generate the default block Agenda.]
2. Notice that the line of equal signs separating the two blocks of
the Agenda is not wrapped. <== CORRECT
3. M-x customize-option RET fringe-mode RET
4. Click the Value Menu button and choose "Left only".
5. Click the Apply button.
6. If the Agenda buffer is no longer visible switch to it (or just
run org-agenda again).
7. Notice that the line of equal signs is now wrapped. <== INCORRECT
Note that setting visual line mode is not really needed for the
recipe, it just makes the problem easier to see. When visual line
mode is not on a $ sign is displayed at the end of the overlong
lines to show they are truncated, and that is not as glaring an
error as when they are wrapped.
Regards,
N.
next prev parent reply other threads:[~2022-04-18 19:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-18 13:10 [BUG] Off-by-one error in width of Agenda window? [9.5.2 (release_9.5.2-25-gaf6f12 @ /data/installs/snapshots/emacs-28.1/lisp/org/)] N. Jackson
2022-04-18 13:39 ` Ihor Radchenko
2022-04-18 19:06 ` N. Jackson [this message]
2022-04-19 3:16 ` Ihor Radchenko
2022-04-19 14:06 ` [BUG] Off-by-one error in width of Agenda window? N. Jackson
2022-04-20 4:01 ` Ihor Radchenko
2022-04-20 10:07 ` N. Jackson
2022-04-21 5:25 ` [PATCH] org-agenda: Use `window-max-chars-per-line' instead of `window-width' Ihor Radchenko
2022-04-21 7:16 ` N. Jackson
2022-04-21 7:56 ` N. Jackson
2022-04-22 5:58 ` [PATCH v2] org-agenda: Use `window-max-chars-per-line' to calculate max text width Ihor Radchenko
2022-04-22 8:42 ` N. Jackson
2022-04-22 9:27 ` Ihor Radchenko
2022-04-22 15:46 ` N. Jackson
2022-04-24 7:04 ` Ihor Radchenko
2022-04-24 11:55 ` Thank you " N. Jackson
2022-04-18 14:30 ` [BUG] Off-by-one error in width of Agenda window? [9.5.2 (release_9.5.2-25-gaf6f12 @ /data/installs/snapshots/emacs-28.1/lisp/org/)] Tory S. Anderson
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o80yqkhi.fsf@moondust.localdomain \
--to=nljlistbox2@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@gmail.com \
/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/org-mode.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).