Discussion:
[notepad-plus - Open Discussion] Stop claiming notepad++ supports Tcl
(too old to reply)
SourceForge.net
2009-05-14 16:40:44 UTC
Permalink
Read and respond to this message at:
https://sourceforge.net/forum/message.php?msg_id=7392045
By: juliannoble

Notepad++'s so called 'support' for Tcl is woeful.

Tcl is theoretically a simple language syntax wise - but getting syntax highlighting
right for such a dynamic scripting language is tricky - and I don't think the
notepad++ devs recognize this.

Notepad++ doesn't match closing brackets properly when the bracketed contents
contain escaped brackets/quotes.

The notepad++ folding system doesn't understand Tcl style comments properly
- e.g by incorrectly recognizing an 'if' on a commented line.

Notepad++ recognizes c-style comments within Tcl. This is just wrong. /* is
a common sequence in filesystem and xml work. It's not a comment in Tcl. Neither
is //.

I'd normally just submit a bug report - but browsing the notepad++ reports -
it's clear you're either not listening or just don't care about Tcl. If you
don't care - fine. But don't pretend Tcl is a supported language.

bug 1362466 - closed - yet still present in V 5.3.1
bug 1653066 - closed presumably because it mentioned a plugin - but if someone
had bothered to actually try it out they might have noticed that folding fails
for a procedure containing a single or double quote. (minor bug - but still
supports my claim that Tcl support is being glossed over)

bug 1993287 - closed - donho claims it was 'fixed', suggesting you have to manually
update your langs.model.xml file. However.. this bug is still present in V 5.3.1
*fresh install*. I don't see how you could close this bug when a simple test
would have shown you it's still there.


bugs
1589507 from 2006
1829963 from 2007
1953192 from 2008
All 3 are open - all related to the awful state of comment highlighting for
Tcl.
A 2008 comment on the 2006 bug even suggests a possible fix which didn't make
it into the release.
This was mentioned on the mailing list last year too:
http://www.mail-archive.com/notepad-plus-***@lists.sourceforge.net/msg01526.htm
l


Someone else submitted a bug report with the title: "Notepad++ hates TCL" and
I can understand why they said that.









______________________________________________________________________
You are receiving this email because you elected to monitor this forum.
To stop monitoring this forum, login to SourceForge.net and visit:
https://sourceforge.net/forum/unmonitor.php?forum_id=331753
SourceForge.net
2009-05-14 16:56:31 UTC
Permalink
Read and respond to this message at:
https://sourceforge.net/forum/message.php?msg_id=7392066
By: juliannoble

Sorry... I come across as pretty grouchy in the above post.. but just
to clarify:
If I was pushed to answer whether I really wanted notepad++ just to drop Tcl
- I'd say no.. but i'ts borderline.
Tcl is still an important language in many fields - and under active development
- but clearly it has a much smaller percentage of users than other languages
so I understand why it would get less attention.

I guess my point is that it would be better if projects wouldn't claim support
for Tcl if it's not fairly robust or being maintained. People already love to
misunderstand Tcl - and it doesn't help that toolmakers seem to assume Tcl support
is 'easy' and do only a rudimentary implementation.
My purpose was more to draw attention to the current state of affairs re notepad++
Tcl support than to genuinely request you dump Tcl.. but If there really aren't
the resources to work on it - I'd still count removal of Tcl from the list of
notepad++ supported languages as a step forward of sorts.

Cheers,
Julian

______________________________________________________________________
You are receiving this email because you elected to monitor this forum.
To stop monitoring this forum, login to SourceForge.net and visit:
https://sourceforge.net/forum/unmonitor.php?forum_id=331753
SourceForge.net
2009-05-14 17:52:13 UTC
Permalink
Read and respond to this message at:
https://sourceforge.net/forum/message.php?msg_id=7392159
By: mike_hinson

Many Cisco routers come with an embedded TCL shell, so TCL may become more
prominant.

______________________________________________________________________
You are receiving this email because you elected to monitor this forum.
To stop monitoring this forum, login to SourceForge.net and visit:
https://sourceforge.net/forum/unmonitor.php?forum_id=331753
SourceForge.net
2009-05-23 18:35:29 UTC
Permalink
Read and respond to this message at:
https://sourceforge.net/forum/message.php?msg_id=7406464
By: donho

Tested with v5.3.1, the comment symbols '#' are added as expected.
It'll be great to check the latest release before whining.

Don

______________________________________________________________________
You are receiving this email because you elected to monitor this forum.
To stop monitoring this forum, login to SourceForge.net and visit:
https://sourceforge.net/forum/unmonitor.php?forum_id=331753
SourceForge.net
2009-05-24 14:59:01 UTC
Permalink
Read and respond to this message at:
https://sourceforge.net/forum/message.php?msg_id=7407397
By: juliannoble

"It'll be great to check the latest release before whining. "

And it'd be great if you'd assess the entire bug report before dismissing it.

Ok.. I'll admit my tone hasn't been great.. and really - I do respect that
you're putting in a lot of time for what may often be a thankless or tedious
task.

The relevant part of the bug 1953912 is the 2nd part - which refers to
the "completely garbled syntax coloring after the first /* encountered".

This still occurs in V 5.3.1





______________________________________________________________________
You are receiving this email because you elected to monitor this forum.
To stop monitoring this forum, login to SourceForge.net and visit:
https://sourceforge.net/forum/unmonitor.php?forum_id=331753
SourceForge.net
2009-05-24 15:21:19 UTC
Permalink
Read and respond to this message at:
https://sourceforge.net/forum/message.php?msg_id=7407419
By: juliannoble

As you've apparently closed further comments for that bug - I'll post some further
details here to assist.

Below is a snippet of Tcl code which demonstrates the issue. The code below
comes from the file tcl/lib/tcl8.6/tm.tcl which is distributed with Tcl itself.


Notepad++ highlights in green, everything from the /* onwards.
It is inappropriate to recognize and attempt to highlight the C-style comments
/* or // in Tcl code - whether they occur within double quotes or other
contexts.


set pos [lsearch -glob $newpaths ${p}/*]
# Cannot use "in", we need the position for the message.
if {$pos >= 0} {
return -code error \
"$p is ancestor of existing module path [lindex $newpaths $pos]."
}



______________________________________________________________________
You are receiving this email because you elected to monitor this forum.
To stop monitoring this forum, login to SourceForge.net and visit:
https://sourceforge.net/forum/unmonitor.php?forum_id=331753
SourceForge.net
2009-05-24 22:35:21 UTC
Permalink
Read and respond to this message at:
https://sourceforge.net/forum/message.php?msg_id=7407778
By: gr3gw

Hi Julian,

I think the root of this issue is that there is confusion between the purpose
of these forums. It serves end-users, developers and beta testers.

When the NP++ team put out a new beta, all the feedback on the new beta is put
on these forums. Some people do not realise that once a beta is out, the team
are no longer focused on the current Official Release (OR). What they would
be interested in is if the problem is occurring on the new beta.

Those of us who are working on the documentation side of the project realise
this and we are preparing a new forum system, which will separate end-users
comments from those of beta testers. We will also make it much clearer what
the current OR version is.

Hang in there.



______________________________________________________________________
You are receiving this email because you elected to monitor this forum.
To stop monitoring this forum, login to SourceForge.net and visit:
https://sourceforge.net/forum/unmonitor.php?forum_id=331753
SourceForge.net
2009-05-24 22:50:30 UTC
Permalink
Read and respond to this message at:
https://sourceforge.net/forum/message.php?msg_id=7407782
By: donho

Now your report is much more constructive.
This bug will be fixed in v5.4, which will be released in a few hours.

Don

______________________________________________________________________
You are receiving this email because you elected to monitor this forum.
To stop monitoring this forum, login to SourceForge.net and visit:
https://sourceforge.net/forum/unmonitor.php?forum_id=331753

Continue reading on narkive:
Loading...