unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Akib Azmain Turja <akib@disroot.org>
Cc: 59963@debbugs.gnu.org
Subject: bug#59963: 29.0.50; 'window-max-chars-per-line' doesn't always work on GUI without fringe
Date: Sun, 11 Dec 2022 16:43:02 +0200	[thread overview]
Message-ID: <83sfhmt30p.fsf@gnu.org> (raw)
In-Reply-To: <87edt6dwgq.fsf@disroot.org> (bug-gnu-emacs@gnu.org)

> Date: Sun, 11 Dec 2022 17:13:41 +0600
> From:  Akib Azmain Turja via "Bug reports for GNU Emacs,
>  the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
> 
> 'window-max-chars-per-line' doesn't always work on GUI when fringe width
> is set to zero.  Although it returns seemingly correct answer, actually
> writing that characters results in the continuation/truncation glyph to
> appear, decreasing the text area width.
> 
> I don't know precisely what condition needs to be meet for trigger the
> bug.  But I think this is triggered when the width of the text area of
> window in character is a fraction.  For example, my window is 1366px
> width, each character takes 8px; so my window is 170.75 characters
> width, and this triggers the bug.
> 
> This bug affects Term, Eat, Eat in Eshell, Coterm in Shell mode, Vterm,
> and possibly any other Emacs terminal emulator.
> 
> Reproduction steps:
> 
> 1.  Run the command 'emacs -nw -Q' in any of the terminal emulators
>     listed above.
> 2.  Remove fringes with 'M-: (set-window-fringes nil 0 0)'.
> 3.  To make the bug is even more clear, enable 'visual-line-mode'.
> 4.  If everything seem to be OK, resize the window.

I tried reproducing the problem, but couldn't:
window-max-chars-per-line returns a value correctly truncated to the
number of fully visible characters that can be shown on the line,
minus the continuation/truncation glyph if there should be one.

So please provide a complete recipe, and please show the numbers: what
does window-max-chars-per-line report when you do what needs to be
done to demonstrate the issue.  Bonus points for demonstrating the
issue without running any terminal emulators, but just by typing
characters (which should produce the same effect, since Emacs display
doesn't really know what Lisp program produces the characters it needs
to display).

Thanks.





  reply	other threads:[~2022-12-11 14:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-11 11:13 bug#59963: 29.0.50; 'window-max-chars-per-line' doesn't always work on GUI without fringe Akib Azmain Turja via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-11 14:43 ` Eli Zaretskii [this message]
2022-12-11 14:50   ` Akib Azmain Turja via Bug reports for GNU Emacs, the Swiss army knife of text editors
     [not found]   ` <87o7sac78t.fsf@disroot.org>
2022-12-11 15:21     ` Akib Azmain Turja via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-11 16:14       ` Eli Zaretskii
2022-12-12  8:18         ` martin rudalics
2022-12-12 13:10           ` Eli Zaretskii
2022-12-12 16:50             ` martin rudalics
2022-12-14 15:21             ` Eli Zaretskii
2022-12-15 15:53               ` Akib Azmain Turja via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-17 12:05                 ` Eli Zaretskii

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=83sfhmt30p.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=59963@debbugs.gnu.org \
    --cc=akib@disroot.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).