Bug in ROXTerm?

Forum › Forums › Official Releases › antiX-21/22 “Grup Yorum” › Bug in ROXTerm?

Tagged: 

  • This topic has 9 replies, 5 voices, and was last updated Dec 9-7:52 am by seriousness.
Viewing 10 posts - 1 through 10 (of 10 total)
  • Author
    Posts
  • December 8, 2022 at 5:51 pm #95174
    Member
    berndE

      Vi (neovim) is behaving strangely in ROXTerm. Whenever you type “:” to get into command mode, garbage appears in the line (see screenshot), which is quite annoying. It seems to be a bug in ROXTerm, since it doesn’t happen in an xterm window.

      Attachments:

      1. screenshot-1.jpg

      December 8, 2022 at 6:02 pm #95178
      Moderator
      Brian Masinick
        Helpful
        Up
        0
        ::

        I just ran nvim, a.k.a. neovim in a roxterm and it worked fine for me. I checked the TERM variable; mine is set to VT200. Check to see what your setting happens to be; perhaps that’s why your instance is not displaying properly. If you don’t want to set TERM in your shell initialization file, you can run TERM=vt200 nvim and that should work, or you can add an entry in whatever startup shell you use; for example, if bash, put TERM=value in .bashrc. It doesn’t have to be vt200, but it has to be something that will properly evaluate the escape sequences to work properly with the terminal and the editor.

        --
        Brian Masinick

        December 8, 2022 at 6:03 pm #95179
        Moderator
        BobC
          Helpful
          Up
          0
          ::

          Are you sure ROXTerm has such a thing as “command mode”?

          December 8, 2022 at 6:15 pm #95180
          Member
          PPC
            Helpful
            Up
            0
            ::
            BobC wrote:

            Are you sure ROXTerm has such a thing as “command mode”?

            The OP is referring to vi’s “command mode”, inside roxterm – and it’s working ok, here, on antiX 19, I just tested it…

            P.

            December 8, 2022 at 6:21 pm #95181
            Moderator
            Brian Masinick
              Helpful
              Up
              0
              ::

              Also, if your screen has color support, TERM=ansi nvim .bashrc (for example), works even better than vt200 because it provides COLOR support.

              --
              Brian Masinick

              December 8, 2022 at 6:22 pm #95182
              Moderator
              Brian Masinick
                Helpful
                Up
                0
                ::

                Yes, as PPC also stated, I also checked out the use of “:” (command mode) and it works just fine.

                --
                Brian Masinick

                December 8, 2022 at 6:36 pm #95184
                Moderator
                Brian Masinick
                  Helpful
                  Up
                  1
                  ::

                  BTW both vim and nvim work fine in this same environment. Same with their graphical interface versions, should anyone have an interest in using them.

                  --
                  Brian Masinick

                  December 8, 2022 at 7:18 pm #95187
                  Member
                  berndE
                    Helpful
                    Up
                    0
                    ::

                    I can confirm that TERM=ansi helped. It had been set to ‘xterm’, probabely by myself. Have to look into my init scripts.

                    December 8, 2022 at 9:44 pm #95200
                    Moderator
                    Brian Masinick
                      Helpful
                      Up
                      0
                      ::
                      berndE wrote:

                      I can confirm that TERM=ansi helped. It had been set to ‘xterm’, probabely by myself. Have to look into my init scripts.

                      Glad to hear that this helps!

                      --
                      Brian Masinick

                      December 9, 2022 at 7:52 am #95227
                      Member
                      seriousness
                        Helpful
                        Up
                        0
                        ::

                        I had the same issue when I invoked vim.tiny as vi. The solution is to set TERM variable to gnome-256color in ROXTerm Preferences.

                      • Author
                        Posts
                      Viewing 10 posts - 1 through 10 (of 10 total)
                      • You must be logged in to reply to this topic.