unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: zeycus <miguelgarciadiaz@ono.com>
Subject: Re: emacs in xterm
Date: Wed, 1 Nov 2006 00:43:23 -0800 (PST)	[thread overview]
Message-ID: <7109844.post@talk.nabble.com> (raw)
In-Reply-To: <878xivacec.fsf@lion.rapttech.com.au>


Just now I found a kind message from Michaël pointing this out.
I apologize, I was completely unaware of this fact. As I explained
I am a newbie in Linux, so I naively thought
that GNU Xemacs was a sort of adaptation of GNU Emacs in X.
Now I see these are different things, but there was no offense
intended in my message, just plain ignorance.

Thank you for kindly making the situation clear to me.




Tim X-2 wrote:
> 
> zeycus <miguelgarciadiaz@ono.com> writes:
> 
>> Wow, thank you for the opinions and suggestions! I am not sure yet,
>> whether or not I want to "jump" to the xemacs multi-window system,
>> but I'll give it a try!
> 
> Note that Emacs and Xemacs are two totally *different* programs. GNU
> Emacs can be built with and without X windows support. Most Linux
> distributions include an Emacs and an Emacs-nox (or something
> similar). The emacs with window support can also be run without the
> X windows features using the -nw switch. 
> 
> Xemacs can only be run on an X windows system (i.e. you cannot run it
> in a term or on the console etc). It represents a fork from the
> original emacs sources which occured some years ago. While the two
> emacs flavors are very similar, there are a number of internal
> differences between the two, such as how they handle font locking. Its
> not unusual to find elisp packages which have tests to determine if it
> is running under GNU Emacs or Xemacs and then does flavor specific
> stuff - this allows an elisp package to work under both systems. 
> 
> HTH
> 
> Tim
> -- 
> tcross (at) rapttech dot com dot au
> _______________________________________________
> help-gnu-emacs mailing list
> help-gnu-emacs@gnu.org
> http://lists.gnu.org/mailman/listinfo/help-gnu-emacs
> 
> 

-- 
View this message in context: http://www.nabble.com/emacs-in-xterm-tf2528263.html#a7109844
Sent from the Emacs - Help mailing list archive at Nabble.com.

  parent reply	other threads:[~2006-11-01  8:43 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.348.1162049311.27805.help-gnu-emacs@gnu.org>
2006-10-28 15:45 ` emacs in xterm Colin S. Miller
2006-10-28 17:01   ` zeycus
2006-10-28 15:51 ` jmg3000
2006-10-28 16:59   ` zeycus
2006-10-28 16:42 ` don provan
2006-10-28 18:06   ` David Hansen
2006-10-28 19:24   ` Floyd L. Davidson
2006-10-29  8:20   ` Malte Spiess
2006-10-31 18:10   ` zeycus
2006-11-01  1:37     ` Michaël Cadilhac
     [not found]   ` <mailman.473.1162318249.27805.help-gnu-emacs@gnu.org>
2006-11-01  6:50     ` Tim X
2006-11-01  8:30       ` Floyd L. Davidson
2006-11-02  8:00         ` Tim X
2006-11-01  8:43       ` zeycus [this message]
     [not found]       ` <mailman.10.1162370610.2155.help-gnu-emacs@gnu.org>
2006-11-02  8:06         ` Tim X
2006-10-28 10:16 zeycus

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=7109844.post@talk.nabble.com \
    --to=miguelgarciadiaz@ono.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).