unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Heime <heimeborgia@protonmail.com>
Cc: 72309@debbugs.gnu.org
Subject: bug#72309: propertized-buffer-identification with maximum width
Date: Sun, 28 Jul 2024 17:32:27 +0300	[thread overview]
Message-ID: <86v80pzix0.fsf@gnu.org> (raw)
In-Reply-To: <iFEUY8zCun6oG7bJta0CygLbmfyqJWtm-dtCqNh0Z-0VwjxRNyPmAgt2xH3wTiXBKZp_Su1cdH2vbWd9sIGzReT5ODWaTwJQdQg8yjjz9ec=@protonmail.com> (message from Heime on Sun, 28 Jul 2024 14:19:30 +0000)

> Date: Sun, 28 Jul 2024 14:19:30 +0000
> From: Heime <heimeborgia@protonmail.com>
> Cc: 72309@debbugs.gnu.org
> 
> > > > Your conclusions are wrong.
> > > 
> > > If I put a question on emacs help, would you answer it in
> > > a way that gets things to work ?
> > 
> > 
> > Not me, I don't have time for this, sorry. But I hope someone else
> > will.
> 
> Then all that discussion with me was a waste of your time.  Saying
> I am wrong but not sharing what you have in mind is a bad strategy.

I said much more than that in this discussion.





  reply	other threads:[~2024-07-28 14:32 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-26 19:04 bug#72309: propertized-buffer-identification with maximum width Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-27  5:48 ` Eli Zaretskii
2024-07-27  9:22   ` Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-27 12:05     ` Eli Zaretskii
2024-07-27 12:23       ` Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-27 13:00         ` Eli Zaretskii
2024-07-27 13:08           ` Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-27 13:29             ` Eli Zaretskii
2024-07-27 14:56               ` Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-27 15:27                 ` Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-27 20:49                   ` Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-28  4:55                     ` Eli Zaretskii
2024-07-28 10:55                       ` Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-28 12:18                         ` Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-28 12:29                           ` Eli Zaretskii
2024-07-28 12:51                             ` Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-28 14:07                               ` Eli Zaretskii
2024-07-28 14:19                                 ` Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-28 14:32                                   ` Eli Zaretskii [this message]
2024-07-28 14:40                                     ` Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=86v80pzix0.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=72309@debbugs.gnu.org \
    --cc=heimeborgia@protonmail.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.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).