[erlang-questions] How to disable parentheses matching in Erlang shell?

Grzegorz Junka list1@REDACTED
Sun May 15 14:00:09 CEST 2016


This is what I said, it isn't broken only for me. I saw it being broken 
on other people's computers as well.

It's unlikely for any scripts to set COLUMNS since I don't see that 
environment variable being set when running shell.

I am running Konsole on the same system on which I am running Erlang, 
both on FreeBSD. I don't need to SSH anywhere. But the behaviour was the 
same no matter from where or to where I was SSH-ing or not (or someone I 
saw doing it), e.g.:

Windows putty SSH to FreeBSD

Windows putty SSH to Ubuntu

Windows putty SSH to Red Hat

Windows putty SSH to CentOS

Windows xterm cygwin SSH to FreeBSD

Windows xterm cygwin SSH To Ubuntu

Windows xterm cygwin SSH to Red Hat

Windows xterm cygwin SSH to CentOS

FreeBSD xterm SSH to Ubuntu

FreeBSD Konsole SSH to Ubuntu

FreeBSD xterm SSH to FreeBSD

FreeBSD Konsole SSH to Ubuntu

FreeBSD xterm SSH to CentOS

FreeBSD Konsole SSH to CentOS

FreeBSD Konsole and Erlang shell on the same system (no SSH)

FreeBSD xterm end Erlang shell on the same system (no SSH)

Ubuntu SSH to CentOS

It's fair to say that I haven't see a system on which this feature 
worked fine, I just learned to not type commands that are too long or 
copy-paste longer commands, and I bet most people who experience it do 
the same and don't bother complaining. I wonder if maybe this has 
something to do with escape codes and for example support for 256 colors 
in the terminal.


On 14/05/2016 22:49, Joshua Barney wrote:
> It seems unlikely that erlang shell is broken only for you on all these systems.
> Have you checked that your shell scripts are not setting COLUMNS? Perhaps you are ssh-ing from a client that is doing something not quite right?
> Sent from my iPhone
>> On May 14, 2016, at 6:39 PM, Grzegorz Junka <list1@REDACTED> wrote:
>>> On 14/05/2016 21:19, Kenneth Lakin wrote:
>>>> On 05/14/2016 03:32 AM, Grzegorz Junka wrote:
>>>> Fixing my terminal to 80 characters only seems like taken straight from
>>>> the Windows world. I hope Erlang can do better ;)
>>> If ncurses can't determine your terminal size, then falling back to
>>> 80x24 makes a lot of sense. Do other ncurses-based programs behave
>>> incorrectly?
>> No. Everything else is fine. This problem is not related to my system, as I have seen the same behaviour in Erlang running on FreeBSD, Ubuntu, Red Hat and CentOS in different terminals, like putty, cygwin and Konsole.
>>>> Is there any way of
>>>> telling the Erlang terminal how wide is my terminal, e.g. an environment
>>>> variable?
>>> On my system, it looks like the environment variables LINES and COLUMNS
>>> correspond to the current size of my terminal window. When I set COLUMNS
>>> to a value that does not match the window's current size, then the
>>> Erlang shell's paren matching bounces the cursor backwards to the wrong
>>> place (but back forwards to the right place). Maybe this will be the
>>> band-aid you need.
>> I don't have such environment variables in my system and I don't remember having them on Ubuntu or Red Hat (however I can't double-check that now)
>>> However, it might be more useful to fix whatever is preventing ncurses
>>> from determining the terminal size.
>> Yeah, and even more useful if the Erlang shell allowed me to disable a feature that isn't really necessary especially if it isn't working correctly.
>> _______________________________________________
>> erlang-questions mailing list
>> erlang-questions@REDACTED
>> http://erlang.org/mailman/listinfo/erlang-questions

More information about the erlang-questions mailing list