Comment Added after submission: synopsis (Score 1) 1
Here is a somewhat more "official" synopsis from the publisher http://physics.aps.org/synopsis-for/10.1103/PhysRevLett.108.110801
Here is a somewhat more "official" synopsis from the publisher http://physics.aps.org/synopsis-for/10.1103/PhysRevLett.108.110801
As part of the society, you should think about how not to become a target of hacking activism. Especially when it's impossible to crush every one of the "hackers".
Better yet, convert them into your loyal customers, and even better, direct their anger to your competitors.
Shell history doesn't contains only input, not output.
Someone may have splashed some GPG private keys to the terminal, and the output ends up in the filesystem blocks.
On a memory-limited system, one may not want
The problem is your terminal history may include data from other hosts, decrypted. Therefore it's not just "your" worries.
Whenever I heard of Japanese speech-jamming machines I go grab my point-of-view gun.
Good luck explaining to the corporate suites what a "pwn" is.
We still see this kind of XXXX coming up every leap year.
eMacs not good enough? But I never know vi costs so much!
I think LyX is mostly focused on the WYSIWIG aspect. Your problems (automatic completion of bibtex key, automatically managed "make" process, and debugging in context) are better solved in something that work like an IDE. Perhaps you can look for one that suites your needs.
Oh come on, get an IDE*. Typo in BibTeX key? It will jump to the offending line and highlight the error. Multiple passes? It manages the compilation process for you.
* Perhaps should be called IAE -- intergrated authoring environment. Personally I use vim-latex but please don't burn me for not using Emacs.
For many purposes, simple text file is indeed superior due to, well you guess, textuality. Put it this way: you can't grep an ODF file, but you can grep in a text file with insane efficiency (most of the time).
Maybe they got a patent on searching *by* the keys instead of searching for the keys. People these days are crazy.
Real Programmers don't write in PL/I. PL/I is for programmers who can't decide whether to write in COBOL or FORTRAN.