From: "FRC" <frc--NoSpAm--@myrealbox.com>
Subject: Re: GNU NTEmacs and X
Date: Sun, 3 Aug 2003 13:41:05 +0200 [thread overview]
Message-ID: <bgiscc$tk9$1@news-reader2.wanadoo.fr> (raw)
In-Reply-To: u7k5wgs7p.fsf@jasonrumney.net
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1808 bytes --]
I indeed would like to be able to run un-cygwinized NTEmacs both with X and
no X.
The pb with cygwinized Emacs is for instance that it doesn't deal with NT
paths eg. C:\foo\bar. I can work around that wirh /cygdrive or a /c mount
point, but I'd rather not. I don't want it to pretend to be on *NIX, but
rather to be able to understand *NIX world.
BTW, I got a strange error when trying to build NTEmacs from CVS sources
with cygwin (make bootstrap)
-----------------------------------
gcc -c -I/usr/share/gettext -Demacs -DHAVE_CONFIG_H -DUSE_LUCID -I. -I/ho
me/FRC/emacs/src -I/usr/share/gettext -I/usr/X11R6/include -g xterm.c
xterm.c: In function `x_create_toolkit_scroll_bar':
xterm.c:4488: `XtNbeNiceToColormap' undeclared (first use in this function)
xterm.c:4488: (Each undeclared identifier is reported only once
xterm.c:4488: for each function it appears in.)
make[1]: *** [xterm.o] Error 1
make[1]: Leaving directory `/home/FRC/emacs/src'
make: *** [bootstrap] Error 2
-----------------------------------
Googled a bit but didn't find anything. I got almost all latest cygwin
packages (apart from games etc...).
Rookie Q: what's that DOC file used for?
FRC
<jasonr (Jason Rumney) @ f2s.com> a écrit dans le message de
news:u7k5wgs7p.fsf@jasonrumney.net...
> Eric Hanchrow <offby1@blarg.net> writes:
>
> > I've had trouble (whose details I forget) sharing byte-compiled Lisp
> > between the NT and Cygwin versions of Emacs.
>
> Were they different versions? There should be no difference in byte
> format between different platforms. I have successfully shared lisp
> directories between Windows and GNU/Linux installations for years.
> And recently someone fixed the DOC file differences between *nix and
> W32, so the CVS version should be able to share that without problems
> as well.
>
prev parent reply other threads:[~2003-08-03 11:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-27 18:28 GNU NTEmacs and X FRC
2003-07-27 19:44 ` Kai Großjohann
2003-07-28 5:59 ` Eli Zaretskii
2003-07-28 14:20 ` X platform clipboard? Bruce Ingalls
2003-07-28 16:07 ` FRC
[not found] ` <mailman.572.1059368245.8231.help-gnu-emacs@gnu.org>
2003-07-28 16:12 ` GNU NTEmacs and X FRC
2003-07-31 21:04 ` Jason Dufair
2003-08-01 20:39 ` Kai Großjohann
2003-08-01 22:03 ` Kevin Rodgers
2003-08-01 22:15 ` Eric Hanchrow
2003-08-02 12:27 ` Jason Rumney
2003-08-03 11:41 ` FRC [this message]
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='bgiscc$tk9$1@news-reader2.wanadoo.fr' \
--to=frc--nospam--@myrealbox.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).