all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 32169@debbugs.gnu.org
Subject: bug#32169: 27.0.50; Wishlist: cleanup of thread-last-error
Date: Mon, 16 Jul 2018 17:55:31 +0200	[thread overview]
Message-ID: <87pnzni39o.fsf@gmx.de> (raw)
In-Reply-To: <83sh4j8ak8.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 16 Jul 2018 18:28:07 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

Hi Eli,

>> > How about having thread-last-error clear the error as a side effect,
>> > perhaps when called with an optional argument?
>
> Should be easy to do, I think.

[...]

> I was certain we had on master a function ti return the main thread,
> but I guess I was dreaming.  We could easily add it, though.

Do you want to do it, or shall I? I know, you are overloaded ...

master or emacs-26 branch? I believe threads are not used widely, so we
won't break any code with Emacs 26.

> In any case, I think it could be a good idea to describe this
> technique in the ELisp manual.

Will do, once the changes above have arrived.

>> PS: Maybe I shall push this to a git branch, giving people a chance for
>> early tests. `find-file-noselect' survives already in simple cases, w/o
>> an Emacs crash.
>
> SGTM, thanks.

Later this week. Tomorrow, or on Wednesday, I'll be busy with merging
shadowfile.el.

Best regards, Michael.





  reply	other threads:[~2018-07-16 15:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-16  7:18 bug#32169: 27.0.50; Wishlist: cleanup of thread-last-error Michael Albinus
2018-07-16 14:34 ` Eli Zaretskii
2018-07-16 14:49   ` Michael Albinus
2018-07-16 15:28     ` Eli Zaretskii
2018-07-16 15:55       ` Michael Albinus [this message]
2018-07-16 18:03         ` Eli Zaretskii
2018-07-16 18:20           ` Michael Albinus
2018-07-17 10:05           ` Michael Albinus
2018-07-17 15:46             ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87pnzni39o.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=32169@debbugs.gnu.org \
    --cc=eliz@gnu.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.