Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: "Robert D. Crawford" <rdc1x@comcast.net>
Subject: Re: How many use eMacs and Gnus on daily basis?
Date: Sat, 10 Jun 2006 15:01:25 -0500	[thread overview]
Message-ID: <87r71wwzje.fsf@comcast.net> (raw)
In-Reply-To: <m3odx11pin.fsf@hawaii.rr.com>

Joe Bush <bushj004@hawaii.rr.com> writes:

>>I don't even run a window manager.  I just start emacs from my .xsession
>>file.  I am not saying that this will work for everyone.  If you are
>>used to point-clicky interfaces you might not like emacs.  Manipulating
>>graphics files is, I believe, a no-go, but viewing them works.
>
> Can you explain how this is done, or provide a link that describes the
> steps?

Really it's just as Tim said.  I log into the machine via a console.  I
don't run [xgk]dm.  After I log in I issue the command

startx

which starts x.  My .xsession file looks like this,:

/*  next line begins .xsession */

#!/bin/bash
# I am not sure that I need this anymore, as I don't
# use anything but emacs.  Take a look at the man page
# for xrdb to see what it is for.
xrdb ~/.Xdefaults

# I have remapped the capslock key to be a super key, and the 
# browser next and back buttons on my Thinkpad to perform emacs 
# functions
xmodmap ~/.Xmodmap

# I can see enough to tell that there is a sliver of the root 
# window that is not covered by emacs, therefore I set it to be
# black
xsetroot -solid black

# if you wanted to start a wm from here, in this case, fvwm, here 
# is how to do it.
#exec fvwm

# Instead, I run a script that starts emacs with emacspeak
exec emacspeak

/*  end .xsession file  */

Then, just as Tim said, when you exit emacs, you exit x, which will take
you back to the console or the x login manager.

rdc

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Robert D. Crawford                                      rdc1x@comcast.net

  parent reply	other threads:[~2006-06-10 20:01 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-07 14:34 me
2006-06-07 14:41 ` Hadron Quark
2006-06-07 15:05   ` me
2006-06-07 15:19     ` Hadron Quark
2006-06-07 15:40     ` Mark T.B. Carroll
2006-06-09  8:17       ` Tim X
2006-06-09  9:46         ` rambam
2006-06-07 15:46     ` Ted Zlatanov
2006-06-07 15:46     ` Malte Spiess
2006-06-09  8:13     ` Tim X
2006-06-09 13:49       ` me
2006-06-07 14:50 ` Mark T.B. Carroll
2006-06-07 15:48 ` David Z Maze
2006-06-07 15:49 ` Robert D. Crawford
2006-06-07 17:49   ` notbob
2006-06-08  8:09     ` Glyn Millington
2006-06-10  6:41   ` Joe Bush
2006-06-10  9:17     ` Tim X
2006-06-10 20:01     ` Robert D. Crawford [this message]
2006-06-12 17:27       ` Joe Bush
2006-06-08  0:57 ` Joe Fineman
2006-06-08  1:17   ` Bastien
2006-06-08  1:40   ` Johan Bockgård
2006-06-08  6:18     ` David Kastrup
2006-06-08  1:59   ` Robert D. Crawford
2006-06-08  3:03   ` me
2006-06-08 14:30     ` David Z Maze
2006-06-08 14:57       ` David Kastrup
2006-06-08 17:58       ` notbob
2006-06-08 18:33         ` David Kastrup
2006-06-08 14:46     ` Eric Eide
2006-06-09  8:27   ` Tim X

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=87r71wwzje.fsf@comcast.net \
    --to=rdc1x@comcast.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).