The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: iking@killthewabbit.org (Ian King)
Subject: [TUHS] Unix taste (Re:  terminal - just for fun)
Date: Sat, 2 Aug 2014 11:51:12 -0700	[thread overview]
Message-ID: <CAF65FFD-0F0F-4FB0-9F0C-DB57E9FE6C9C@killthewabbit.org> (raw)
In-Reply-To: <20140802164748.6D3BD18C0B2@mercury.lcs.mit.edu>

On Aug 2, 2014, at 9:47 AM, Noel Chiappa wrote:
>
> Does something like Word produce the same reaction for you? I don't  
> use it
> much, but my wife does (she's an engineer, and uses it to write  
> papers), and
> its complexity drives her crazy sometimes.
>

After writing my general exam in MS-Word,  I swore off it unless  
forced to use it (i.e. collaborative requirements).  When a stupid  
but ambitious application program thinks it's smarter than you are  
and tries to 'correct' your writing (I now call it 'autocorrupt'),  
it's time to change.  These days I write in EMACS and format with  
LaTeX, printing in PDF.  I can't imagine writing my dissertation with  
the turd called Word.

Unfortunately, I have to keep MS-Worst on the family computer,  
because the public schools require parents to purchase for-profit  
software to support our children's education.  (There are too many  
incompatibilities with Open Office et al. that trip up my less- 
computer-savvy family members for the open-source tools to be a  
useful alternative in an compulsory MS world.)  Fortunately, I get it  
for free through *my* school.

For programming, I used to use exclusively vi, but tried EMACS out of  
curiosity and found its UI to be a less constrained than vi's modal  
approach.  I use Gnu, FWIW.  -- Ian

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20140802/00b8cb79/attachment.html>


  reply	other threads:[~2014-08-02 18:51 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-02 16:47 Noel Chiappa
2014-08-02 18:51 ` Ian King [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-08-06 22:24 Norman Wilson
2014-08-06 22:19 Norman Wilson
2014-08-04 20:21 Norman Wilson
2014-08-04 22:24 ` A. P. Garcia
2014-08-05  2:41   ` Andy Kosela
2014-08-05  3:32     ` Warner Losh
2014-08-04  2:54 Norman Wilson
2014-08-04  3:11 ` Lyndon Nerenberg
2014-08-04  7:04   ` Dave Horsfall
2014-08-04  9:12     ` Steve Nickolas
2014-08-03 16:48 Noel Chiappa
2014-08-03 17:09 ` John Cowan
2014-08-03 11:49 Noel Chiappa
2014-08-03 12:14 ` Steve Nickolas
2014-08-03 16:26 ` John Cowan
2014-08-04 13:59 ` Tim Bradshaw
2014-08-04 14:53   ` A. P. Garcia
2014-08-03  0:48 Noel Chiappa
2014-08-03  8:00 ` A. P. Garcia
2014-08-02 21:18 Noel Chiappa
2014-08-02 23:44 ` A. P. Garcia
2014-08-02 14:28 Doug McIlroy
2014-08-02 14:00 ` Larry McVoy
2014-08-02 15:51   ` Steve Nickolas
2014-08-02 16:07     ` John Cowan
2014-08-02 17:28     ` Benjamin Huntsman
2014-08-02 19:50     ` Dave Horsfall
2014-08-02 16:04 ` Diomidis Spinellis
2014-08-02 16:03   ` Larry McVoy
2014-08-02 19:36 ` Dave Horsfall

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAF65FFD-0F0F-4FB0-9F0C-DB57E9FE6C9C@killthewabbit.org \
    --to=iking@killthewabbit.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).