Hacker Newsnew | past | comments | ask | show | jobs | submit | groks's commentslogin

Emacs has org-mode, and org-mode has tables with formulas which can invoke calc-mode. calc-mode also has units:

https://www.gnu.org/software/emacs/manual/html_node/calc/Uni...


A bit of Fry and Laurie, on language:

https://www.youtube.com/watch?v=3MWpHQQ-wQg


With the built-in winner-mode you can go back to the previous window layout with C-c left.


> (H)Ledger does not support recurring transactions.

https://www.ledger-cli.org/3.0/doc/ledger3.html#Periodic-Tra...


Use your thumb.


Specifically your right thumb if you're not a touch typist.


> The things that I don't feel as comfortable with are basically UI things and application launching. I love Cmd-space to launch stuff on OSX, and hitting the Windows key to search for stuff to launch just feels sluggish in comparison.

In Gnome, Hit the Windows key and start typing 'shortcut' to run the keyboard shortcut editor.

Start typing 'application' to search-ahead-find the 'Show all applications' shortcut and click it.

Press Cmd-space.


  cat << EOF > ~/.config/gtk-3.0/gtk.css

  /* Make window title bars more compact.
   *
   * From: https://unix.stackexchange.com/questions/276951
   */

  headerbar entry,
  headerbar spinbutton,
  headerbar button,
  headerbar separator {
      margin-top: 2px; /* same as headerbar side padding for nicer proportions */
      margin-bottom: 2px;
  }

  EOF



TIL, thank you!


Gtk has a Mir backend, GNOME Shell does not.


If you enable server-mode you can run gui emacs to get the icon in the doc and pop up a gui window when you drop something on it, while also connecting in a terminal.


> The true metric for success for something like ntpsec is the number of meaningful security problems ntpd has been vulnerable to since ntpsec's inception that ntpsec hasn't been.

They talk about 3 areas where bugs have been removed, including:

  Much of ntpd’s most convoluted code lives in ntp_proto.c, which
  implements the state machine central to the protocol. Of the 29
  vulnerabilities that have received CVEs so far in 2016, a couple
  of multi-KLOC functions in ntp_proto.c are responsible for 15 of
  them — just over half. Of course, "just rip it out" wouldn’t
  suffice in this case: this is core business logic, not junk code.
  So we rewrote those functions from scratch, cutting line count
  considerably and yielding a far more readable result.
https://blog.ntpsec.org/2016/12/13/fantastic-bugs-and-where-...

The other two areas are guaranteed bug-free because they removed the code.


From this paragraph you might get the impression that ntpsec had dodged 29 CVEs in 2016. But that's not the impression I have: I think it has been vulnerable to many of the bugs reported in ntpd.

Further: not all CVEs are equivalent, so in addition to wanting to know how many vulnerabilities ntpsec was also vulnerable to, you also want to know what the distribution both of severity and of exposure in the default configuration those bugs had.

Ultimately: I feel about ntpsec the way I would have felt if, in 1997, someone had proposed SendmailSec. The answer to the Sendmail security problem wasn't a "hardened" Sendmail (though the Sendmail team sure tried); it was Postfix and qmail.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: