unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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: Wed, 31 Jul 2019 00:45:54 +0200	[thread overview]
Message-ID: <87d0hruonx.fsf@pointsman.de> (raw)
In-Reply-To: <87muv5n841.fsf@tromey.com> (Tom Tromey's message of "Thu, 05 Jul 2018 07:07:58 -0600")


Tom Tromey <tom@tromey.com> writes:
>>>>>> "Rolf" == Rolf Ade <rolf@pointsman.de> writes:
>
> Rolf> Indent the second line ("foo") with <Tab> and you get
> Rolf> do {
> Rolf>     foo
>
> Thanks for trying this.
> I suppose instead of the fix for the "namespace" thing, tcl-mode should
> maybe just looking at brace depth for indentation.  I will take a deeper
> look.

Despite #32035 this is still open with master of today (but not with
26.2). Completely legal and commen code at the beginning befor the first
word out of tcl-proc-list are not indented as expected. Examples:

do {
something
}

if {$argc != 0} {
puts stderr "usage: $argv0"
}

set options {
-foo "default"
-bar "bardefault"
}


Expected indentation would be of course something like:

do {
    something
}

if {$argc != 0} {
    puts stderr "usage: $argv0"
}

set options {
    -foo "default"
    -bar "bardefault"
}


After the first word out of tcl-proc-list in the buffer all that
examples above will be indented as expected, no misbehaviour any more.

I happily confirm again, that master hasn't the original problem of this
bug report. And I'd really love to see that fixed, after it has plagued
me for 20 years.

But I'm afraid that the cure (current behavior of master) is worse than
the problem (26.2).





  reply	other threads:[~2019-07-30 22:45 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
2018-07-04 22:10     ` Rolf Ade
2018-07-05 13:07       ` Tom Tromey
2019-07-30 22:45         ` Rolf Ade [this message]
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=87d0hruonx.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).