Explore >> Select a destination
|
You are here 
|
arunmani.in | ||
| | | | |
codeinthehole.com
|
|
| | | | | A short guide to getting things to look nice | |
| | | | |
www.danielallington.net
|
|
| | | | | [AI summary] The discussion revolves around the use of LaTeX for writing and typesetting, with a focus on its strengths and weaknesses. Key points include the readability of LaTeX code versus text, the role of LaTeX in scientific publishing, and the debate over whether LaTeX is suitable for writing prose. Some users argue that LaTeX is more efficient for complex formatting and typesetting, especially in academic contexts, while others find it cumbersome for everyday writing tasks. The conversation highlights the importance of choosing the right tool for the task, with LaTeX being particularly well-suited for specific needs like mathematical notation and document structure, but not necessarily for general writing. There is also a mention of the challenges of ... | |
| | | | |
blog.computationalcomplexity.org
|
|
| | | | | By request a post that may create the biggest backlash since I declared myself Unixfree . \begin{rant} LaTeX is a great system for mat... | |
| | | | |
vxlabs.com
|
|
| | | Recently, as I replaced more of my Emacs-helm configuration with counsel and ivy, I noticed that ivy-switch-buffer, when augmented by ivy-rich, was not showing the directories of the buffers it was listing. After some Lisp spelunking, I discovered that it was because ivy-rich relies on the presence of either the projectile package, something I do not wish to have in my Emacs configuration, or on project.el, which I also do not use. In this post, I show how you can get full buffer filenames and project na... | ||
