13 ms·
Windows: "Everything" (that's the name). A lightweight, fast and advanced (if you want it) file search engine. Linux: Most tools of course, as they are made wi
by lucb1e 10y ago
Windows: "Everything" (that's the name). A lightweight, fast and advanced (if you want it) file search engine.
Linux: Most tools of course, as they are made with the Unix philosophy, but these days I'm most surprised by print drivers for Linux. Where in Windows the printer is always magically offline or slow, from Linux I can print and scan very reliably.
Vim is also worth learning, it makes editing much more... relaxed I guess. No longer have to move your mouse to the arrow keys or even the mouse/touchpad to scroll or select. It also helps that it exists on nearly every Unix system you'll ever connect to.
And finally I recently discovered LaTeX, which could be described as markdown on steroids. A little more difficult to get into, but it's easy to create professional documents and have a plain text source (which works nicely with git and other unix tools). If you have trouble getting started in LaTeX, ask me (comment here or see my profile), I also didn't know how to get started for a while.
Edit: Another Windows tool is Notepad++. I have not seen the likes in Linux when it comes to robustness. It has all the basics you need for handling any sort of file that involves manual editing, binary or plain text. If there is no binary editor available for your file of choice, or if you just want to have a quick peak, Notepad++ will do just fine. Beware of really huge files, although I have seen it handle some big things on low RAM machines too.
- barsonme 10y agoIf you've any latex pointers I'd appreciate it :) I used latex to write a paper for the first time last week, and while i thoroughly enjoyed it, i'm fairly confident there were lots of things I could've done better.
- lucb1e 10y agoI've written two papers in it now, so I'm not a grandmaster yet either. If you managed what you wanted to do and enjoyed it, you probably know as much as me. I'm not sure there is really a wrong way to use it. If you google every little thing to find a good solution (not manually inserting and formatting references for example), I don't think there is too much to be done better. At least, to my beginner's eyes it doesn't seem like it.
- dbcurtis 10y agoI've recently discovered Quiver. Mac only, but open file format spec (if you are feeling particularly energetic). But it certainly is the nicest thing I've found for doing LaTeX.
- pigscantfly 10y agoI would recommend trying www.writelatex.com.
- jloughry 10y agoUse makefiles and git with LaTeX. Use \input{} to structure large documents as a main file that includes smaller ones. Keep all your BibTeX citations in one large .bib file (under git) and symlink it into the current directory for every new document; it makes bibliographies so much easier. PDFLaTeX makes it incredibly easy to keep all your graphics in PDF files; it makes them so much nicer to deal with. Inkscape is great for making vector graphics for use in LaTex; keep the source code of the graphics in SVG but save as PDF for LaTeX to use (tell Inkscape to export only the drawing to PDF, not the whole page, and you'll never have to crop or resize your graphics ever again). Finally, use a modern TeX like XeTeX that directly understands Unicode characters and TrueType fonts.
- justinlardinois 10y agoI second git and Make, but I'm not sure I agree with the single .bib file thing. That works if you're writing a lot of documents on the same subject that use many of the same sources, but that's a very specific use case.
- barsonme 10y agoOooh, I like the .bib idea. I might steal it and use it for select things---I decided it'd be a good idea to go back (sorta) and finish my BS, so creating one for each class might be a very good idea. Import as .pdf not .svg? Got it. It was tricky fiddling with percentages and stuff to get the .svg to fit properly (and look decent). Thanks! I'll look into XeTex.
- Analemma_ 10y agoIME, the most important key to Latex is setting up your environment so you can have a fast turnaround time between writing some markup and seeing what it looks like (essentially, getting a "Latex REPL"). There are a bunch of different ways to do this, you'll have to pick what's best for you. On Macs I tend to use Sublime Text (substitute with your editor of choice) with a macro to invoke pdfTeX; on Windows I use TeXstudio which has live preview support. There are other ways; do whatever's best for you. The second most important thing I've found for latex is setting up macros. In TextExpander/AHK I have several dozen Latex macros set up, like \tbl3 => \begin{tabular}{ l | c | r } a & b & c \\ \end{tabular} With a bunch of variants for different styles (full borders, etc.), column numbers, etc. Once your macros have become muscle memory, writing Latex speeds up considerably.
- barsonme 10y agoYeah, that makes sense. I'll make sure to do that. It was kind of time-consuming typing out the couple tables I did add. I used latexmk which watches file(s) for changes and rebuilds with pdflatex. It was nice, but made my laptop run real hot, and inotify never really works very well. Which ST plugin do you use?
- eivarv 10y agoNot OP, but I've had good experiences with LaTeXTools[1]. [1]: https://packagecontrol.io/packages/LaTeXTools https://packagecontrol.io/packages/LaTeXTools
- majewsky 10y agoOn Linux, I do the following: while inotifywait *.tex; do sleep 0.2 && pdflatex main.tex && killall -HUP mupdf; done This will, when a .tex file is written, wait a moment until all disk IO is done, then run pdflatex and trigger a reload in my PDF viewer (some also do that automatically when the .pdf file is changed). The only annoyance is that big .tex files (esp. Beamer presentations) may take long to compile, which interrupts the flow. But in that case, it helps to distribute the sources into multiple files and to comment out the source files that are not needed at the moment.
- akincisor 10y agoThe only LaTeX link you'll need: https://tobi.oetiker.ch/lshort/lshort.pdf https://tobi.oetiker.ch/lshort/lshort.pdf
- justanotherbody 10y agoI'm pretty weak at LaTeX but if you haven't used macros and rerender-on-write I'd strongly recommend it The latter is something i achieved with sleep_until_modified.sh and a shell loop. Pretty rudimentary but functionally equivalent to modern webdev reload-on-write behavior. HUGELY beneficial to my learning latex syntax and behavior and formatting nuances
- avn2109 10y agoIMHO the best TeX tutorials on the internet are written by some Helpdesk guy on his blog: http://www.terminally-incoherent.com/blog/2010/02/15/lets-learn-latex-part-1/ http://www.terminally-incoherent.com/blog/2010/02/15/lets-le... I'm not affiliated in any way with that site but the pedagogy is very approachable. Also it helps to use a site like WriteLatex.com or ShareLatex.com to do the hard setting up part when you're just starting out. Edit: I see he is no longer a helpdesk guy, and his blog's tagline is (unfortunately) no longer "I will not fix your computer."
- barsonme 10y agoThat looks great, thank you for sharing!
- geff82 10y agoUse TeXstudio to write your documents. It is an IDE with autocompletion and contextual help and an integrated viewer. Made writing LaTeX so much easier, as it also has wizards to generate repeating boilerplate. I love Latex, especially mathematical notations are a breeze.
- stirner 10y agoMany resources have been suggested, but not the guide written by the creator of TeX and computer science legend Donald Knuth: http://www.ctex.org/documents/shredder/src/texbook.pdf http://www.ctex.org/documents/shredder/src/texbook.pdf
- stirner 10y agoMany resources have been suggested, but not the guide written by the creator of TeX and computer science legend Donald Knuth: http://www.ctex.org/documents/shredder/src/texbook.pdf http://www.ctex.org/documents/shredder/src/texbook.pdf
- taserian 10y agoAdding to the list of editors: LyX is a great cross-platform editor that I've used. https://www.lyx.org/ https://www.lyx.org/
- sssilver 10y agoVim departs from the reliability camp once you start adding a bunch of plugins. But as a raw editor, yes -- it's solid.
- majewsky 10y agoThen you're using the wrong plugins. I have about 12 here and can't recall any stability problems.
- acoard 10y agoReliability != stability (in this context). I can reliably ssh into pretty much any server and use default vim. I cannot rely on a given plugin to be installed on the server. The more you customize vim, the less universal your knowledge of vim becomes. It's not a big deal to learn some plugins, but it is worth bringing up if people are talking about the ubiquity of it.
- nostrademons 10y agoFWIW, I used to use Notepad++ back around 2005 and it was a piece of crap stability-wise. Frequent crashes, and not-infrequent UI glitches like syntax highlighting just stopping working. This isn't a reflection on its state now, but I'm trying to make the point that good software takes time. They've had 13 years to clean it up now, and evidently it's gotten a lot better. But that's worth remembering when judging the crap software that's come out in the last couple years. Linux printing also used to absolutely suck, so much that CUPS was generally synonymous with the hassles you (used to) need to go through to do practical work with a Linux system. Ubuntu has been an absolute godsend in terms of getting a stable, productive Linux desktop working.
- jpindar 10y agoI use Notepad++ all the time and I've never had any problems at all. Granted, I don't use many of its features, I mostly just edit plain text. Its select by columns feature is useful though.
- zeta0134 10y agoSeriously, if Ubuntu were a single piece of software, it would top my charts. I don't even use it regularly anymore except on my work Desktop (I run Arch linux on all my personal machines) but the sheer level of "Just Works(tm)" is mind boggling. It quite handily picks up my weird wireless cards and video devices without fuss, and I haven't managed to fully break an Ubuntu installation (mostly dealing with nVidia back in the day, when it was less magical to get working) in a way that I couldn't easily revert. I realize a lot of that is riding on the Debian team, but Canonical has done some fantastic work just testing the thing out on such a wide variety of configurations. It's the distribution I recommend to any of my friends looking to try Linux out for the first time.
- simbalion 10y agoI recommend Debian for similar reasons. It might not be as magical as Ubuntu but it still works out-of-box for a variety of common hardware and is built on a great free as in free philosophy.
- blakeyrat 10y agoI don't enjoy using software that's difficult to learn or use, which most of your examples seem to be. (I haven't used "Everything", so I might be wrong about that one.) Notepad++ used to cheese me off in a previous job where I was basically forced to use it because it couldn't even draw drop-down menus correctly. Ugh. Terrible UI.
- loco5niner 10y ago"Everything" really is that simple. Point it at some folders and go.
- lucb1e 10y agoFolders? It's extremely quick to index whole drives, so I'd just let it do just that.
- loco5niner 10y agoTrue. That is what is does by default, and does it well.
- nojvek 10y agoDoes anyone know how everything work? Does it hook into the NTFS filesystem with special apis? The indexing is insanely fast. I wonder how they make it happen.
- boduh 10y agoIt reads the NTFS Master File Table (MFT) which contains records for all files and folders. It only does this the first time it runs (or when you manually tell it to rebuild the index). It also uses the NTFS USN journal [1] in order to update changes to its index so that it doesn't need to read the MFT and rebuild the index every time it runs. [1] https://msdn.microsoft.com/en-us/library/windows/desktop/aa363798%28v=vs.85%29.aspx https://msdn.microsoft.com/en-us/library/windows/desktop/aa3...
- lucb1e 10y agoIt's actually really ironic that it's so much faster than Windows' own search.
- vardump 10y ago> Edit: Another Windows tool is Notepad++. I have not seen the likes in Linux when it comes to robustness. It couldn't even open a 1.2 GB text file when I tried it yesterday. On a 32GB system. Seriously?
- lucb1e 10y agoIt's been a while since I last used it, but I thought it could handle files that big. At least on systems with 2GB ram or so, it would open files of hundreds of megabytes just fine. Not sure I ever tried anything over a gigabyte, but I might have.
- shermanyo 10y ago> Vim is also worth learning, it makes editing much more... relaxed I guess. No longer have to move your mouse to the arrow keys or even the mouse/touchpad to scroll or select. It also helps that it exists on nearly every Unix system you'll ever connect to. People often talk about the speed of use, but this is (IMO) a result of its efficiency. I liked your use of the word 'relaxed', I'd add: slow down your actions so you have time to think about what you're doing, almost like narrating your actions. Vim has a grammar that works well when spoken. Learn Vim's way of saying the action you're performing, then learn the relevant keys, adding them to your vocabulary. If a sentence makes sense in your head, try it and it'll probably work as expected. Say you started with: "delete 3 words" == d3w "yank to the end of the line" == y$ From this you could assume these valid: "delete to the end of the line" == d$ "yank 5 words" == y5w It takes time, but it builds up when you add a word to your vocab here and there, when you have a concrete use for it. (often one you'll remember from the 'wow, that was cool' moment when you first see it in action)
- oxplot 10y agoSome more examples: "delete inside quotes" == di" "select all of the block" == va{
- Sir_Cmpwn 10y agoWhen I just want a quick peek at a binary file on Linux I use `hexdump -C filename | less`.
- majewsky 10y agoFor hexdump, I could never remember which switch gives me the format that I want to see. I'm now using xxd, which comes with vim and has nice defaults.
- lucb1e 10y agoSure there are hex converters and editors for Linux, but Notepad++ is a text editor that handles binary as if it were just another text file. For example if you try in Vim to edit binary files beyond very simple edits, it'll usually corrupt them. And from `hd file.bin | less` you can't edit them.
- deleted 10y ago[deleted]
- enthdegree 10y agoLatex does not belong on the list. I have not been using it as long as many, but it does not meet OP's description at all. It's entire premise is to put the focus on writing, but at that it fails miserably. Left to over 30 years of growth outside of its intended use case, LaTeX proper does nothing you would need it to, and the packages that you use with it are horribly fragmented. Maybe Latex is good at the things it sets out to implement, but those things aren't what I or anyone else uses it for (creating publication-quality documents). So in considering latex we are forced to also consider the environment of libraries it exists in. LaTeX brings all the problems you had in the Windows 2000 era of programming into document creation. All your favorites like misleading compiler messages, dependency hell, choosing a compiler, knowing whether or not you have run the compiler enough times to produce a final document (!!!), bad compile environments, inconsistent naming, inconsistent syntax for passing parameters to library calls (!!!), GOTOs. There is no way to write semantic latex for most documents where you would need it. Here's a fun project: find a way to reference the same footnote or endnote multiple times throughout a document in a way consistent with how you reference anything else (that is, using \label and \ref). Some arcane technicality in the way the counter is set up prevents you from doing this. Instead, you have to create your own global counter, write a function to maintain it, then use this function in lieu of LaTeX's implementation of footnotes. Every time I want to do anything other than add words to my document, I have to think about whether I want to use Latex's meager facilities, facilities that I had to write, or facilities that someone else invented, then worry about all the quirks in them. If I want to add a table to my document, I need to decide whether it should be a `tabular', `tabular* ' `tabularx', `align', `array', `eqnarray', or `matrix'. Someone has told me once that one of these is very bad and should be avoided unless absolutely necessary, although he didn't tell me why, and I don't remember which one. If I want to make a cell span two columns, I have to remember whether that is the `multicols' package, or the `multicolumn' package. If my table gets too big, I now have to hard-code a split myself, or repeat the entire process and convert my table to a `longtable'. I hope I don't have to wrap anything in a `minipage'. It baffles me that thinking about these things is prerequisite to creating a document. The attitude that 'LaTeX is easy' is perpetrated loudly by people that haven't had to use LaTeX very much. It is only tentatively saved by the comprehensive (sometimes, if you're lucky, even readable) documentation of all its quirks. I am not going to stop using Latex, but no one will ever get me to say that it's easy.
- enthdegree 10y agoLatex does not belong on the list. I have not been using it as long as many, but it does not meet OP's description at all. It's entire premise is to put the focus on writing, but at that it fails miserably. Left to over 30 years of growth outside of its intended use case, LaTeX proper does nothing you would need it to, and the packages that you use with it are horribly fragmented. Maybe Latex is good at the things it sets out to implement, but those things aren't what I or anyone else uses it for (creating publication-quality documents). So in considering latex we are forced to also consider the environment of libraries it exists in. LaTeX brings all the problems you had in the Windows 2000 era of programming into document creation. All your favorites like misleading compiler messages, dependency hell, choosing a compiler, knowing whether or not you have run the compiler enough times to produce a final document (!!!), bad compile environments, inconsistent naming, inconsistent syntax for passing parameters to library calls (!!!), GOTOs. There is no way to write semantic latex for most documents where you would need it. Here's a fun project: find a way to reference the same footnote or endnote multiple times throughout a document in a way consistent with how you reference anything else (that is, using \label and \ref). Some arcane technicality in the way the counter is set up prevents you from doing this. Instead, you have to create your own global counter, write a function to maintain it, then use this function in lieu of LaTeX's implementation of footnotes. Every time I want to do anything other than add words to my document, I have to think about whether I want to use Latex's meager facilities, facilities that I had to write, or facilities that someone else invented, then worry about all the quirks in them. If I want to add a table to my document, I need to decide whether it should be a `tabular', `tabular', `tabularx', `align', `array', `eqnarray', or `matrix'. Someone has told me once that one of these is very bad and should be avoided (unless absolutely necessary), although he didn't tell me why, and I don't remember which one. If I want to make a cell span two columns, I have to remember whether that is the `multicols' package, or the `multicolumn' package. If my table gets too big, I now have to hard-code a split myself, or repeat the entire process and convert my table to a `longtable'. I hope I don't have to wrap anything in a `minipage'. Someone told me once One of these is very bad and should always be avoided. It baffles me that thinking about these things is prerequisite to creating a document. It is only tentatively saved by the comprehensive (sometimes, if you're lucky, even readable*) documentation of all its quirks. The attitude that 'LaTeX is easy' is perpetrated loudly by people that haven't had to use LaTeX very much. I am not going to stop using it, but no one will ever get me to say that it's easy.
- kek918 10y agoThanks for the tip about "Everything". Tried it for the first time now and, oh boy my life just changed. This is incredible! I'd like to see that quick ASCII search implemented into Windows. The included webserver is also fantastic.
- raveren 10y agoIf we're talking windows software, since moving on I really really miss Irfanview, it's ridiculous for how long it's been actively developed by one person. It's featherweight, does its job admirably and has a myriad of advanced options when - and only when you need them.