1. 22

  2. 5

    Any chance it will support the language server protocol?

    1. 3

      A small nitpick about the site: Please link, prominently, to the repository.

      I had to literally use a web search engine just so that I could see the code.

      1. 4

        In case someone missed it, the GitHub repo isn’t being maintained anymore. Just in case someone made the same mistake as I did.

        1. 1

          What do you mean by “isn’t being maintained anymore”? There is a lot of activity, the most recent from earlier this week: https://gitlab.com/craigbarnes/dte/-/commits/master/

          1. 5

            github vs gitlab.

      2. 2

        Tried it out, by opening some source code of mine.

        What stood out immediately were huge blank areas. It turns out, when using a black terminal background (the default in many terminal emulators, including Linux fbcon and *bsd wscons), the comments are invisible because they are rendered black.

        First impressions are excellent otherwise, but this is a deal breaker.

        1. 2

          It’s a little bizarre, then, that the screenshot on the home page has a black background.

          1. 2

            Done a few further experiments. This is with dte-1.9.1-2 from Arch’s AUR:

            Problem under:

            • xterm -fg orange -bg black with and without tmux in the middle
            • linux framebuffer console

            Works fine:

            • konsole

            I have to assume it doesn’t affect the author, but these use cases where it’s broken are important.

        2. 2

          When I think about what a programmer’s editor needs, from first principles (trying to keep out preconceptions as a Vim user), this feature list feels quite complete. The only thing I can imagine missing is the ability to record and rerun keyboard macros. Does dte provide those?

          1. 3

            Not a problem in trunk

            1. 1

              Nice. Just built it. Builds super easy. I also love this:

              Some pre-built, portable binaries are available for Linux. They’re statically-linked with musl libc and require nothing of the host system except a somewhat recent kernel.

              (Bottom of https://craigbarnes.gitlab.io/dte/releases.html)

              1. 1

                Geek’s joke:

                If micro editor is micro,
                then dte editor is nano.
                1. 2

                  Isn’t the nano editor nano?

                  1. 1

                    I just tried to open a .scm file, and <M-x>show option<CR> shows that it recognizes the filetype to be scheme. However, there’s no colorization. I think it’s because there’s no scheme file at https://gitlab.com/craigbarnes/dte/-/tree/master/config/syntax. Anybody interested in collaborating to contribute one? Here’s what I have so far (based on reading https://gitlab.com/craigbarnes/dte/-/blob/master/docs/dte-syntax.md and cribbing from https://gitlab.com/craigbarnes/dte/-/blob/master/config/syntax/python):

                    syntax scheme
                    state start code
                      char ; comment
                      eat this
                    state comment
                      char "\n" start
                      eat this

                    Unfortunately it’s not yet having any effect. It’s not that I need to recompile the project. I wonder if I need to register the new file somewhere.

              2. 1

                I couldn’t find any mention of autoindent, or a mechanism by which it could be added. that’s a strong requirement for me.

                1. 3

                  Good point, but FYI I’m trying it out and autoindent does exist.