From: Rolf Ade <rolf@pointsman.de>
To: Tom Tromey <tom@tromey.com>
Cc: 23565@debbugs.gnu.org
Subject: bug#23565: 24.5; tcl-end-of-defun and tcl-eval-defun doesn't work reliable
Date: Mon, 02 Jul 2018 14:04:13 +0200 [thread overview]
Message-ID: <87zhz99742.fsf@pointsman.de> (raw)
In-Reply-To: <871scw3x6g.fsf@tromey.com> (Tom Tromey's message of "Sun, 24 Jun 2018 11:35:03 -0600")
I'm sorry for the delay in replying; I was on vacation and saw your mail
just this day, after comming back.
Thank you for taking care!
Tom Tromey <tom@tromey.com> writes:
> I've checked in a fix for the tcl-end-of-defun problem.
> I think it should fix tcl-eval-defun as well, but I didn't test this.
I've build current master and did a few tests. Yes, it seems, that
tcl-end-of-defun as well as tcl-eval-defun now work for me as expected,
even in the reported-as-broken cases.
I'll copy masters tcl-mode.el over to my currently used 26.1
installation (and bytecompile, of course) and give it a try in my daily
Tcl coding, for a few days, to see, if I stumble over any unexpected
side-effect of the changes.
I'll report in a week or at most two (it varies a bit how much Tcl
coding I have to do and this is driven by others).
rolf
next prev parent reply other threads:[~2018-07-02 12:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-17 22:10 bug#23565: 24.5; tcl-end-of-defun and tcl-eval-defun doesn't work reliable Rolf Ade
[not found] ` <handler.23565.B.146353542425998.ack@debbugs.gnu.org>
2016-05-18 12:40 ` bug#23565: Acknowledgement (24.5; tcl-end-of-defun and tcl-eval-defun doesn't work reliable) Rolf Ade
2016-06-17 3:55 ` bug#23565: " Noam Postavsky
2018-06-24 17:35 ` bug#23565: 24.5; tcl-end-of-defun and tcl-eval-defun doesn't work reliable Tom Tromey
2018-07-02 12:04 ` Rolf Ade [this message]
2018-07-04 22:10 ` Rolf Ade
2018-07-05 13:07 ` Tom Tromey
2019-07-30 22:45 ` Rolf Ade
2019-09-28 0:20 ` Rolf Ade
2019-09-28 17:47 ` Lars Ingebrigtsen
2019-10-13 3:19 ` Lars Ingebrigtsen
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=87zhz99742.fsf@pointsman.de \
--to=rolf@pointsman.de \
--cc=23565@debbugs.gnu.org \
--cc=tom@tromey.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).