Tibleiz

I must, as I always do, bring up my favorite editor Code Browser which works for this to some degree: http://tibleiz.net/code-browser/ I've been using it for some 15 years and I don't think I will ever leave it. I do wish that other editors (vscode in particular) would adopt its folding style or at least enable it. Doesn't seem promising though (https://github.com/microsoft/vscode/issues/17904)

I have used pugixml (based on PugXML) for very fast parsing of very simple XML and I can highly recommend it. The speed and (IMO) interface improvements are very large. http://code.google.com/p/pugixml/ In AsmXML's benchmark, ASM was 14x faster than Xerces (http://tibleiz.net/asm-xml/benchmark.html). In pugixml's benchmark, pugi was 11x faster than Xerces (http://zeux.mooo.com/pub/pugixml/table.html). Not bad for ASM vs C++. Both systems only support a limited subset of XML features.

There are some specialized text editors for editing files with tabs. https://en.wikipedia.org/wiki/Tab_stop#Dynamic_tab_stops , https://nick-gravgaard.com/elastic-tabstops/ , https://tibleiz.net/code-browser/

Another tool in the space that almost no one seems to know: https://tibleiz.net/code-browser/

I like http://tibleiz.net/code-browser/ Haven't tried it on Ubuntu though.

I think Pogoscript, Argile and Zinc allow spaces. http://pogoscript.org/guide/variables.html http://www.nongnu.org/argile/ http://tibleiz.net/zinc/identifiers.html

Agreed. I initially thought he was referring to editors like Leo (http://leoeditor.com/) or Code Browser (http://tibleiz.net/code-browser/), but now I'm not sure.

To answer my own questions about the intended use for "Code Browser", see: http://tibleiz.net/code-browser/tips.html Understanding existing source code Code Browser can help you to understand existing source code. There is a lot of tools dedicated to program understanding that will do the job better than Code Browser, but if the source code is written in a too obscure language or too old, it can be a cheap alternative. Here is some tips to make more sense of a flat text file by extracting a structure and reducing its apparent complexity:

Identifiers with blanks: http://tibleiz.net/zinc/ (not that strange, but not so common)

You might want to have a look at this: http://tibleiz.net/asm-xml/index.html It's a fast (200MB/sec) XML parser/decoder in pure x86 assembler.

For those who like leo/literate programming, have a look at code-browser: http://tibleiz.net/code-browser/ More powerful overall. It implements elastic tabstops too! Little unknown gem. good for outlining a book/paper also.

You can do useful things with Code Browser, it has folding and links. Aka, it is the simplest possible form of a hypertext. As it is just text, things can easily be scripted. https://tibleiz.net/code-browser/download.html I have kept an older, personally preferred version of that Editor on my GitHub Repo, unfortunately it does not perform stable on Linux and I have not been able to compile it on that system, in order to fix the bugs. https://github.com/nilslindemann/Code_Browser_49/blob/master/README_EN… Here is a video showing how it works (my older version + scripts): https://www.youtube.com/watch?v=sU4ThIJ6eKc I also use this editor for code, it gives me the expressiveness I need, but its comments make the code look terrible in other editors. I wish these features were available in other text editors. For someone used to Code Browsers folding capabilities, other editors are just awkward. But I guess other Coders will think the same when they see that they don't even get completion in Code Browser. Also, it is quite a niche editor.

Something like this https://tibleiz.net/code-browser/ maybe?

I agree, this can be summarised as "abstraction hides bugs". I believe that although abstraction is a powerful tool, there is such a thing as too much of it, and when reading an XML document can cause access to other files, maybe even across the network, perhaps things have gone a little too far. This isn't like an obvious #include or @import, it's much more subtle. When I first noticed that HTML doctypes have URLs in them, I inquisitively tried accessing them, and it brought up a lot of questions in my mind about why it was designed that way, what would happen if the URLs no longer existed, etc. Such an explicit external dependency just didn't feel right to me. Unfortunately most people either don't notice or seem to ignore these things... Interestingly enough, not all XML parsers support external entities; the first one to come to mind is this: http://tibleiz.net/asm-xml/introduction.html

This was for fun (as he says.) > Remember: if you really need speed, do not use XML. He defines his own schema language, in XML (not XML Schema), which the parser needs. Nothing wrong with that. You could even transform (some subset of) XSD's to it using XSLT. (see "2. defining the schema" http://tibleiz.net/asm-xml/tutorial.html and "defining the schema" http://tibleiz.net/asm-xml/documentation.html) He stores attributes in an array, to give O(1) access (... if you assume attribute order is significant, which it isn't according to the XML spec and most tools... even though humans find them more readable if in an expected order. So, to find a specific attribute, you'll have to step through them.) XML parsers are unbelievably inefficient.. (but c'mon... it's XML... all other sins pall to insignificance before the big one, as fireflies at dawn.) He makes the nice point that once you have the XML parsed, you can just use those strings directly instead of copying them again. IBM research came out with a this idea a while back, of combining the two, but it doesn't seem to have gone anywhere. I'd guess they patented it like crazy, because, after all, they are IBM. http://portal.acm.org/citation.cfm?id=1135777.1135796 (that's just the abstract - sorry, couldn't find the pdf.) But again, all this cleverness wouldn't matter except that it's fun (if you really need speed, do not use XML.). Oh... and except in "XML appliances":…