9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: John Floren <slawmaster@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Why does Acme only show text?
Date: Wed, 15 Jul 2009 14:07:24 -0700	[thread overview]
Message-ID: <7d3530220907151407r2bdae5dejaa8ca323b0395c64@mail.gmail.com> (raw)
In-Reply-To: <076872D5-BC44-4608-B806-CCFEEA01E8FA@mit.edu>

On Wed, Jul 15, 2009 at 1:58 PM, Chad Brown<yandros@mit.edu> wrote:
>> Emacs is great for writing Lisp. Now, if only I could find the correct
>> .emacs invocation to make the tab key insert a tab character in C
>> mode, rather than a bunch of spaces the way His Holy Lunacy RMS
>> desires. If I wanted spaces instead of tabs, I'd type them!
>
> OT for the list, but this is trivial in emacs for several years now, and RMS
> has nothing to do with the special code for C mode (which is called CC-mode,
> and supports a bevy of languages, and is complicated enough that it can
> probably boot minix on it's own by now).
>
> *Chad
>
>

In the interests of not slandering Emacs excessively, I'd like to
state that I seem to have figured out my .emacs file to a point where
hitting a tab inserts a tab. That will be all.

John
--
"I've tried programming Ruby on Rails, following TechCrunch in my RSS
reader, and drinking absinthe. It doesn't work. I'm going back to C,
Hunter S. Thompson, and cheap whiskey." -- Ted Dziuba



  reply	other threads:[~2009-07-15 21:07 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-15  1:58 Jason Catena
2009-07-15  4:36 ` Rob Pike
2009-07-15  5:02   ` David Leimbach
2009-07-15 13:11   ` Charles Forsyth
2009-07-16  9:58   ` cej
2009-07-16 10:41     ` mattmobile
2009-07-16 12:11     ` michael block
2009-07-16 12:29       ` cej
2009-07-15  9:25 ` Paul Donnelly
2009-07-15 12:22   ` Ethan Grammatikidis
2009-07-15 15:32     ` cej
2009-07-15 15:44       ` Ethan Grammatikidis
2009-07-15 17:00         ` John Floren
2009-07-15 18:24           ` Francisco J Ballesteros
2009-07-15 18:26           ` Steve Simon
2009-07-15 18:59             ` David Leimbach
2009-07-15 19:07               ` John Floren
2009-07-15 19:27                 ` David Leimbach
2009-07-15 20:58                 ` Chad Brown
2009-07-15 21:07                   ` John Floren [this message]
2009-07-15 19:54               ` Jason Catena
2009-07-15 19:59                 ` erik quanstrom
2009-07-15 20:05                   ` andrey mirtchovski
2009-07-15 20:14                   ` Devon H. O'Dell
2009-07-15 20:29                     ` Jason Catena
2009-07-15 20:42                       ` Noah Evans
2009-07-15 20:51                         ` David Leimbach
2009-07-15 21:27                           ` Ethan Grammatikidis
2009-07-15 23:31                             ` Jason Catena
2009-07-15 21:07                         ` Ethan Grammatikidis
2009-07-15 21:12                           ` erik quanstrom
2009-07-15 21:32                             ` Ethan Grammatikidis
2009-07-15 20:41                     ` Lyndon Nerenberg
2009-07-15 21:00     ` Federico G. Benavento
2009-07-15 21:14       ` David Leimbach
2009-07-16  8:51     ` Paul Donnelly

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=7d3530220907151407r2bdae5dejaa8ca323b0395c64@mail.gmail.com \
    --to=slawmaster@gmail.com \
    --cc=9fans@9fans.net \
    /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).