Package Details: eltclsh 1.17-1

Git Clone URL: (read-only, click to copy)
Package Base: eltclsh
Description: interactive shell for the TCL programming language
Upstream URL:
Licenses: BSD
Submitter: tequa
Maintainer: tequa
Last Packager: tequa
Votes: 2
Popularity: 0.000000
First Submitted: 2015-10-25 11:12 (UTC)
Last Updated: 2018-10-10 07:15 (UTC)

Dependencies (5)

Required by (0)

Sources (1)

Latest Comments

ratchet commented on 2017-01-03 02:07 (UTC)

Thanks for responding so quickly! So far your new patch seems to be working for me too. I'll keep testing and comment again if I bump into a problem. Now I understand why eltclsh was working in Debian -- it's libedit is from 2014.

tequa commented on 2017-01-02 18:22 (UTC)

ok - I added a (probably highly experimental) patch. Seemed to be due to libedit changing to wide character whereas some input processing function in eltclsh assumed characters... It seems to work for me now.

tequa commented on 2017-01-02 13:52 (UTC)

I got the same problem but gave up (because I did not use it for a long while and then this input problem came up out of a sudden...) and did not even get as far as you with the hitting enter workaround. But now I started to look around a little and found that the problem probably arose with libedit-20160618_3.1-1 ... going back to libedit-20150325_3.1-2 solves the problem but is not a real solution. I am also trying to look for a solution because this is the best tcl shell I found so far and would like to be able to use it again.

ratchet commented on 2016-12-31 18:52 (UTC) (edited on 2016-12-31 21:29 (UTC) by ratchet)

When I first start the interpreter, all keystrokes appear as unicode symbols, like this: eltclsh > \U+5120A\U+5127F\U+5120A If I immediately press enter, the interpreter seems to work normally from then on -- but will unpredictably relapse into the same behavior after a while. If at first I press any other key than enter, I am stuck with the above and all I can do is ctrl-c out of the program. I can build this version of eltclsh from source in debian and it works as it should. I have tried installing this package on a clean build of arch in virtualbox, and it has the same problem there.