From: Ihor Radchenko <yantar92@posteo.net>
To: Salih Muhammed <lr0@gmx.com>
Cc: "Rudolf Adamkovič" <salutis@me.com>, emacs-orgmode@gnu.org
Subject: Re: Consider removing newlines from org-insert-link help message
Date: Thu, 18 Jan 2024 12:41:56 +0000 [thread overview]
Message-ID: <875xzqak4r.fsf@localhost> (raw)
In-Reply-To: <8734uvi5pu.fsf@gmx.com>
Salih Muhammed <lr0@gmx.com> writes:
> I see that the text has been updated after updating org at my end,
> however, the issue of the stretch persists (see attachment).
>
> My version of org is at 571186631a09262abb58ca395f75b837bbb28888
>
> Org version gives: 9.7-??-5711866
Org does not add any extra newlines there. It is likely something about
window size.
From the screenshot, it looks like you use some window management
package or customized your `display-buffer-alist'. This customization is
likely overriding Org mode's call to `fit-window-to-buffer', making the
window appear larger than the containing buffer text.
I may be wrong though. It would help if you try to reproduce the problem
starting from emacs without customization. See
https://orgmode.org/manual/Feedback.html#Feedback
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
prev parent reply other threads:[~2024-01-18 12:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-17 6:00 Consider removing newlines from org-insert-link help message Salih Muhammed
2023-10-17 10:53 ` Ihor Radchenko
2023-10-17 21:44 ` Salih Muhammed
2023-10-18 10:43 ` Ihor Radchenko
2023-10-20 11:01 ` Rudolf Adamkovič
2023-10-20 12:30 ` Ihor Radchenko
2023-12-10 0:22 ` Rudolf Adamkovič
2023-12-10 14:07 ` Ihor Radchenko
2023-12-10 23:25 ` Rudolf Adamkovič
2023-12-11 11:30 ` Ihor Radchenko
2023-12-17 23:36 ` Rudolf Adamkovič
2024-01-18 5:13 ` Salih Muhammed
2024-01-18 12:41 ` Ihor Radchenko [this message]
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=875xzqak4r.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=lr0@gmx.com \
--cc=salutis@me.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).