# Years followingĮventually, I migrated to Sublime as it's plugin system was awesome throughout the following years I tried out all of the above options I mentioned. Vim and Emacs felt foreign at first, Notepad++ felt clunky, and Sublime for some odd reason was not clicking. I wasn't sticking to one language for an extensive period either so no "holistic IDE" solution felt right. It was a mess, but I persevered swapping editors like hotcakes until I figured out what I liked. Now around 16, with a few years of working in these environments under my belt, I had more insight into what mattered in an editor to me. Instead of focusing on the specific technology or project I was working on at that time, I decided to formalise to myself what I wanted from a general editor. In the end, my list of requirements looked something like this for my dream editor: If you are looking to choose a long-term editor, I think making a list like this is helpful! # Choosing my requirements I was hoping that formalising this list would help me make a more permanent decision as I'd moved around a lot in the years past. I think a lot of these are self-evident, I just had to choose what matted to me. I want to give a bit more context to one of these: cross-platform as it was hugely influential in my decision. Not only did I want something "cross-platform" in that it could run on Windows, OSX, and Linux, but I also wanted something that could work from the CLI and on multiple Linux distros.Ī bit before this I was diving into system administration for the first time. Using a small home server, running on an old desktop from my grandmother, I was diving head-on into a new world. It was huge, exciting, and full of intricate puzzles ready to solve. Where you get one letter wrong and suddenly no results.Fiddling around in nano felt inefficient for certain things, particularly when trying not to use my mouse in the CLI, I needed something better. Fuzzy search should fix that, so I'm glad you have it. We also are currently working on fixing typos. We predict the possibility of the current char being a typo and try to find the word you were trying to type. However, this is also hard and we are still experimenting with it. Sounds like you need a lemmatizer in your indexing, which would give you singular/plural/past/present results for cheap. Synonyms would be a killer feature, though not sure how you'll do that since my synonyms will be different than someone else's. Could you not allow the user to specify their own synonyms in a setting somewhere? Might be a quick win. ![]() We were thinking of having a maximum of 1-2 synonyms per word (the most probable ones) for common words (top 10k words). In our own notes, we are actually adding the synonyms manually. When I write some heading I will add some synonyms so I can find them better. This is a problem that we need to iterate multiple times in order to get right. Otherwise, it will worsen the experience. If you decide to try Nota, I would love to get your feedback! You can write to us at that makes sense and it works now! Thank you so much for the feedback, ideas, and knowledge. I'm not too fond of having to enter a preview mode everytime though, would it be possible to automatically render these tables when not "focussing" on them (by having the cursor inside the table)? I don't know how else to describe it, but I would prefer it much more if they work like the LaTeX $$ blocks (rendered when cursor is elsewhere, expand to reveal the "source code" when clicked, re-render when cursor moves outside again).Įdit: Another thing I just noticed is that when selecting a bunch of lines of text with a LaTeX block somwhere in the selection, the block will first expand when the cursor is moved over the block, but when expanding the selection some more past the block, the rendered LaTeX will appear again. This (visually) creates an interrupted selection highlight and makes understanding what exactly is copied unintuitive in my opinion. I would much prefer it if LaTeX blocks stay unrendered as long as (a part of) it is within a selection. The same would go for tables, if a feature like I said above is ever implemented. Let me know if I should put these requests on GitHub as well. ![]() Though it doesn't have those other features. ![]() I do use it both on iOS and macOS, and when I need those more advanced editing, I will often hop over to BBEdit or the like. Like I said, I do use Notebooks and I think it is criminally under appreciated in the reddit communities I frequent. It is file based, supports things like wiki links (though they could use improvements on generating links), and it is pretty good all together. While it is text based, every tools has its quirks so it is nice that it is also on iOS so that they are similar.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |