unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: kobarity <kobarity@gmail.com>
To: James Thomas <jimjoe@gmx.net>
Cc: Eli Zaretskii <eliz@gnu.org>, 71720@debbugs.gnu.org
Subject: bug#71720: [PATCH] Do not prematurely truncate python eldoc string
Date: Sun, 23 Jun 2024 09:47:58 +0900	[thread overview]
Message-ID: <eke7o77s4h8h.wl-kobarity@gmail.com> (raw)
In-Reply-To: <86msncvg0r.fsf@gmx.net>

James Thomas wrote:
> Eli Zaretskii wrote:
> 
> >> Date: Sat, 22 Jun 2024 23:16:51 +0900
> >> From: kobarity <kobarity@gmail.com>
> >> Cc: 71720@debbugs.gnu.org
> >>
> >> Eli Zaretskii wrote:
> >> >
> >> > kobarity, any comments?
> >>
> >> I agree with this fix.  For those who want the same behavior as
> >> before, setting eldoc-echo-area-use-multiline-p to nil should be
> >> sufficient.  It might be better to make this change known in etc/NEWS,
> >> though.
> >
> > Thanks.
> >
> > James, can you add a NEWS entry and resubmit?
> 
> How about this?

> +*** 'eldoc' no longer truncates to a single line by default.
> +Previously, the entire docstring was not available to eldoc, which made
> +'eldoc-echo-area-use-multiline-p' ineffective. The old behaviour may be
> +kept by setting that.
> +

Thanks, I think the content is perfect, but from other examples, it
might be better to have two spaces after the period.





  reply	other threads:[~2024-06-23  0:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-22 12:44 bug#71720: [PATCH] Do not prematurely truncate python eldoc string James Thomas via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-22 13:03 ` Eli Zaretskii
2024-06-22 14:16   ` kobarity
2024-06-22 15:50     ` Eli Zaretskii
2024-06-22 21:12       ` James Thomas via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-23  0:47         ` kobarity [this message]
2024-06-23  3:02           ` James Thomas via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-23  3:53             ` kobarity
2024-06-27  8:56             ` 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=eke7o77s4h8h.wl-kobarity@gmail.com \
    --to=kobarity@gmail.com \
    --cc=71720@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=jimjoe@gmx.net \
    /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).