353 karma · joined July 12, 2016
Blog: https://scripter.co
* Few projects:
- Org-mode + Hugo: https://ox-hugo.scripter.co
- Eless (A Better less): https://eless.scripter.co
On https://nim-lang.org/faq.html under "What about editor support?", Aporia is mentioned as the first option. Should it be moved lower in the list?
Anyways I use nim-mode in emacs, and it works great!
But they can have the same CSS styling (colors, fonts, responsiveness, etc) that ties the whole site together.
A good example that's at the top of my mind is this: https://hugodocs.info
It works great on desktop as well as phone, and a common theme is seen all across the site.
> the documentation page for example is just composed of a list of links and descriptions.
By the documentation page, I meant a page like this: https://nim-lang.org/docs/manual.html
That's a lot of good info but is not accessible in a good way on phone.
For sort of an equivalent reference, see https://hugodocs.info/templates/base/
It has a similar collection of help pages and the design is responsive too.
Are you considering converting the documentation pages to responsive design too?
Also the black and yellow theme looks great on the home page, but that theme loses its continuity on all the other pages. It's as if the home page was designed by a different person, the feature and other landing pages by someone else, and the documentation pages by someone else altogether.
I have the nim-mode and smart-compile packages installed, and I have bound F9 to compile the nim code in the current buffer, and run it in the emacs-inbuilt eshell.
I have configured so that the point and buffer switching 'does the right thing'.
- If the compilation fails, show the compilation buffer in the other window, and do not execute the binary, and keep the point in the code window.
- If the compilation passes, execute the binary in the other window.
- Now if the binary execution ends with showing the eshell prompt, move the point back to the other window (code window).
- If not, that is, if the eshell prompt does not show up, keep the point in the eshell buffer, because that most likely means that some user input is expected.
---
So my nim learning process goes as: type a code snippet, F9, type more, probably cause error, F9, fix that, F9, etc.
Config: [1] [2]
[1]: https://github.com/kaushalmodi/.emacs.d/blob/master/setup-fi...
[2]: https://github.com/kaushalmodi/.emacs.d/blob/master/setup-fi...
Every git operation I've done is effortless with Magit: interactive rebase, selective staging (line based, not just hunk based), cherry picking, reordering commits and squashing, creating/pushing to/deleting local/remote branches, viewing graphical branch log, .. (list goes on).
The actual power of Emacs is realized once you learn elisp. Coding, documenting, commiting, blogging, browsing, file/dir manipulation, etc. all can be done efficiently using the same familiar buffer editing philosophy within Emacs.
By the way, the Keys to Great Writing is an awesome book. It has made me critique everything I write, in a good way. I even thought twice before submitting this comment.
UPDATE 2: Fix: Use the verb critique rather than critic (one who does that).
I had never heard of Vonnegut before this. Suggestion for a good book by him to start with?
Proof: https://imgur.com/U0Z2aKp
Now it is superceded by avy (by abo-abo on GitHub) in every way + new features.
For such packages that always have room for improvement and not related to core emacs functionality, it is better that they stay in external repositories on GNU Elpa or Melpa.
That way, older packages do not have to get tied with emacs core. Currently Ido package is in that situation. I used to use Ido, but now I use the ivy package instead. Some people prefer to use helm instead. I would not be affected at all if Ido was removed from the emacs core in future and moved to GNU Elpa.