Re: XEmacs as a Cygwin64 package.

On 29/06/2025 23:03, Dan Harkless via Cygwin wrote: [...] To be clear, "32-bit" was a modifier to "Cygwin", not to "XEmacs". There are no more 32-bit Cygwin maintainers, because it's been discontinued, no?  That being said, I downloaded the Cygwin list archives so I could find the last time I

Re: XEmacs as a Cygwin64 package.

On 29/06/2025 17:01, Aidan Kehoe via Cygwin wrote: Dear Cygwin, I am the maintainer of XEmacs; I have recently made a beta release and that beta release has no complication or exection problems that are specifically related to 64-bit Cygwin. Dan Harkless advises me that there is no current 64-

Re: XEmacs as a Cygwin64 package.

Dan Harkless via Cygwin writes: > To be clear, "32-bit" was a modifier to "Cygwin", not to "XEmacs".  > There are no more 32-bit Cygwin maintainers, because it's been > discontinued, no?  That being said, I downloaded the Cygwin list > archives so I could find the last time I asked about this on t

Re: XEmacs as a Cygwin64 package.

On 6/29/2025 9:43 AM, Eliot Moss wrote: On 6/29/2025 12:01 PM, Aidan Kehoe via Cygwin wrote: Dear Cygwin, I am the maintainer of XEmacs; I have recently made a beta release and that beta release has no complication or exection problems that are specifically related to 64-bit Cygwin. Dan Ha

Re: [QUAR] Re: XEmacs as a Cygwin64 package.

Thanks for all that, Aidan! At present I am a committed GNU Emacs user and have too many ongoing projects to undertake XEmacs packing / maintenance anyway, but I hope that your additional information will encourage a volunteer out there! Regards - Eliot -- Problem reports: https://cygwin.c

Re: XEmacs as a Cygwin64 package.

Ar an naoú lá is fiche de mí Meitheamh, scríobh Eliot Moss: > On 6/29/2025 12:01 PM, Aidan Kehoe via Cygwin wrote: > > > I am the maintainer of XEmacs; I have recently made a beta release and > > that beta release has no complication or exection problems that are > > specifically related t

Re: XEmacs as a Cygwin64 package.

On 6/29/2025 12:01 PM, Aidan Kehoe via Cygwin wrote: Dear Cygwin, I am the maintainer of XEmacs; I have recently made a beta release and that beta release has no complication or exection problems that are specifically related to 64-bit Cygwin. Dan Harkless advises me that there is no current 6

Re: xemacs crashes with SIGSEGV after update

Siegmar Gross writes: > >> > today I updated all packages of my 32-Bit Cygwin installation >> (installed >> > on top of Windows 7). After that xemacs crashed if I tried to >> open a >> > file. Therefore I reinstalled the older version >> xemacs-21.4.23.1. >> > Unfortunately the old

Re: xemacs crashes with SIGSEGV after update

Hi, > today I updated all packages of my 32-Bit Cygwin installation (installed > on top of Windows 7). After that xemacs crashed if I tried to open a > file. Therefore I reinstalled the older version xemacs-21.4.23.1. > Unfortunately the older version crashes as well. I can sta

Re: xemacs crashes with SIGSEGV after update

Greetings, Henry S. Thompson! > Run cygcheck -s -v -r > cygcheck.out and include that file as an > attachment in your report. Please do not compress or otherwise > encode the output. Just attach it as a straight text file so that it > can be easily viewed. I've tried to "not compress or o

Re: xemacs crashes with SIGSEGV after update

Siegmar Gross writes: > today I updated all packages of my 32-Bit Cygwin installation (installed > on top of Windows 7). After that xemacs crashed if I tried to open a > file. Can't reproduce. Please follow the instructions at https://cygwin.com/problems.html In particular Run cygcheck -

Re: xemacs crashes with SIGSEGV after update

> Siegmar Gross writes: > Hi, > today I updated all packages of my 32-Bit Cygwin installation (installed > on top of Windows 7). After that xemacs crashed if I tried to open a > file. Therefore I reinstalled the older version xemacs-21.4.23.1. > Unfortunately the older vers

Re: xemacs crash when fontifying files

"Dr. Volker Zell" writes: >> Vin Shelton writes: > > > Is this with 21.4.23? There is a patch in 21.4.23 specifically designed > > to work around this. > > Yes.. Oops. I've just applied a patch to 21.4 to fix this. - Vin -- Problem reports: http://cygwin.com/problems.html

Re: xemacs crash when fontifying files

> Vin Shelton writes: > Is this with 21.4.23? There is a patch in 21.4.23 specifically designed > to work around this. Yes.. > Thanks, > Vin Ciao Volker -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Docu

Re: xemacs crash when fontifying files

Will Parsons writes: > I've recently noticed that xemacs will crash if one attempts to turn on > syntax highlighting via turn-on-font-lock (even started with the -q option), > but only if run under X. (If X is not running, there is no problem.) The > crash causes the following to print: > > Lisp

Re: xemacs crash when fontifying files

> Will Parsons writes: > I've recently noticed that xemacs will crash if one attempts to turn on > syntax highlighting via turn-on-font-lock (even started with the -q option), > but only if run under X. (If X is not running, there is no problem.) The > crash causes the follo

Re: Xemacs: Adding a Font

Never mind. I figured it out. The fonts are installed in Windows. On Mon, Aug 6, 2012 at 7:27 PM, Tom Szczesny wrote: > Thanks Mark (for the Cygwin/X suggestions). > > I went the X-route in Cygwin only because that is what I did in Gentoo. > But Xemacs works perfectly well in Cygwin w/o starting

Re: Xemacs: Adding a font

Tom Szczesny writes: > When I execute the command > xset fp rehash > I get the message: > xset: unable to open display "" [...] > Any suggestions? Questions about X Window on Cygwin belong on the cygwin-xfree list. But the short answer is that 'xset' dynamically (re-)configures the

Re: XEmacs warning

Sorry - I was missing the xemacs-sumo package. Adding that appears to have fixed it. David -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#uns

Re: XEmacs warning

On Mon, Sep 06, 2010 at 05:41:38PM +, Kris Thielemans wrote: > it works perfectly fine for me. I guess you'll have to give some more details > about your installation. (I have no idea what's relevant though...) Hi Kris, thanks for the reply. I am seeing this on two different Window 7 Professi

Re: XEmacs warning

David Morgan writes: > > Hi All, > > I have been getting the following Xemacs error with all 1.7 Cygwin > releases that I > have tried: > > WARNING: > Couldn't find an obvious default for the root of the > XEmacs hierarchy. > > I saw a similar issue came up in 2006, and Dr. Volker Zell

Re: xemacs winclient improvements

2009/6/24 Reini Urban: > * xemacs-21.5.28-3 uses slow defaults: I'm using now: --with-optimization \ --with-modules=yes \ with-optimization is fast enough now for me. with-modules to enable integrat

Re: xemacs failing with exit code 53

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Nathan Thern on 10/24/2008 2:07 PM: > Is there something special I need to do to run xemacs under cygwin? > > If I type 'xemacs' at the command prompt, it silently fails ($? = 53) > It doesn't matter what arguments I give it or what I hav

Re: XEmacs & Dialog Boxes

> Paul Lange writes: > Has anybody successfully opened dialog boxes with Cygwin XEmacs > version 21.4.21 under Cygwin X11 on XP? If I try to click on one of > the toolbar buttons or menu items that loads a dialog box, a brief > flash occurs as a window tries to open and fails.

Re: XEmacs & Dialog Boxes

Paul Lange wrote: Has anybody successfully opened dialog boxes with Cygwin XEmacs version 21.4.21 under Cygwin X11 on XP? All the time, but not using X11, just XEmacs under the Windows XP window manager. If I try to click on one of the toolbar buttons or menu items that loads a dialog box,

Re: xemacs

Taras D wrote: Hi everyone, Can anyone tell me why the following has occurred. When I first installed cygwin, I pretty much just installed xemacs (no emacs and a whole bunch of other stuff). Xemacs could be started from the bash script (black background) with the command 'xemacs &'. It would st

Re: xemacs

Taras D wrote: Hi everyone, Can anyone tell me why the following has occurred. When I first installed cygwin, I pretty much just installed xemacs (no emacs and a whole bunch of other stuff). Xemacs could be started from the bash script (black background) with the command 'xemacs &'. It would st

RE: xemacs marking a buffer as read-only

Hi, I have been having a problem with xemacs running on cygwin and writing to files on a network drive which are handled by a OpenSUSE 10.2 server running samba 3.3. It seems that if the file already existed then there is no problem with editing the file and saving it. But I cannot create

Re: xemacs does not work

> NE writes: > Dear All, > I am trying to use xemacs. After installation of cygwin, I used once > but later it doesn't work. it gives this error: "temacs can only be > run in -batch mode" > what do you suggest? cygcheck -cv xemacs > thanks > regards Ciao Volk

RE: xemacs eshell doesn't automatically append .exe

Thank you. The new eshell fixed the problem. > -Original Message- > From: Dr. Volker Zell > New Packages in Pre-Release: > === > eshell-1.11-pkg.tar.gz upstream version: 2.4.1 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem repo

Re: xemacs eshell doesn't automatically append .exe

> Harry Rockefeller writes: > Most of the internal "compiled Lisp functio" commands work > correctly, but standard UNIX commands don't. > Here is an example: > /cygdrive/c/DOCUME~1/harryr $ w > Opening input file: No such file or directory, /usr/bin/w > /cygdrive/c/DOC

Re: xemacs -nw problem

On Tuesday 08 May 2007 16:36:14 Dave Korn wrote: > > I think you're being a bit over-sensitive there. Some might consider > expecting others to do your most basic homework for you unfriendly, but I Probably and perhaps. In the context of the thread I knew someone could give me a two line answe

RE: xemacs -nw problem

On 08 May 2007 16:28, Andrew Walrond wrote: > On Tuesday 08 May 2007 15:42:35 Dave Korn wrote: >>> >>> PS What's the pupose of the CYGWIN env var? >> >> If you don't know about it, you can't have done even the most basic >> level of RTFMing. See >> > > Not being entirely clueless and with

Re: xemacs -nw problem

On Tuesday 08 May 2007 15:42:35 Dave Korn wrote: > > > > PS What's the pupose of the CYGWIN env var? > > If you don't know about it, you can't have done even the most basic level > of RTFMing. See > Not being entirely clueless and with my unix head on I did (from the bash shell) export CYGW

RE: xemacs -nw problem

On 08 May 2007 15:34, Andrew Walrond wrote: > On Tuesday 08 May 2007 14:50:53 Dr. Volker Zell wrote: >> >> I just had a chance to install cygwin on a new machine. >> Under the default bash shell the CYGWIN environment variable is not >> exported. In that case I can reproduce Andrews xemacs proble

Re: xemacs -nw problem

On Tuesday 08 May 2007 14:50:53 Dr. Volker Zell wrote: > > I just had a chance to install cygwin on a new machine. > Under the default bash shell the CYGWIN environment variable is not > exported. In that case I can reproduce Andrews xemacs problems. > > Exporting CYGWIN=tty resolves the issues. >

Re: xemacs -nw problem

> Eric Blake writes: > According to Dr. Volker Zell on 5/7/2007 8:43 AM: >>> Andrew Walrond writes: >> >> > A minor problem (possible bug): If I try to run xemacs in the cygwin terminal, >> > without an X window, via the -nw option, its behaviour is a little stange

Re: xemacs -nw problem

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Dr. Volker Zell on 5/7/2007 8:43 AM: >> Andrew Walrond writes: > > > A minor problem (possible bug): If I try to run xemacs in the cygwin > terminal, > > without an X window, via the -nw option, its behaviour is a little >

Re: xemacs -nw problem

> Andrew Walrond writes: > Hello list > First off; I've been using cygwin for years, on and off, but this is the first > time I have joined the ML, so I just like to say _fantastic_work_guys_ to all > involved. > A minor problem (possible bug): If I try to run xemacs i

Re: xemacs -nw problem

. Reformatted. Andrew Walrond wrote: > On Wednesday 02 May 2007 14:55:18 Andrew Walrond wrote: >> Hello list >> >> First off; I've been using cygwin for years, on and off, but this is the >> first time I have joined the ML, so I just like to say >> _fantastic_wor

Re: xemacs -nw problem

Is there a better place to report this? How do I find out who maintains the xemacs/cygwin port? Andrew Walrond On Wednesday 02 May 2007 14:55:18 Andrew Walrond wrote: > Hello list > > First off; I've been using cygwin for years, on and off, but this is the > first time I have joined the ML, so I

Re: xemacs forms not like emacs forms

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Rockefeller, Harry on 4/17/2007 10:00 AM: > I define a user function to move between fields in my form (record): > > It runs correctly in emacs but not xemacs. I get this error in xemacs > when I try to save the form: > > Parse error: n

Re: Xemacs warning message after update to xemacs-21.4.19-2

> Kirill Yarosh writes: > Hi all, > After update to xemacs-21.4.19-2 I got a following warning message: > WARNING: > Couldn't find an obvious default for the root of the > XEmacs hierarchy. > It's just a warning but xemacs works properly. Anybody knows h

Re: Xemacs print problem

> Eric Monsler writes: > All, > I have installed the xemacs as part of the cygwin setup. > When trying to print from within xemacs, xemacs crashes and fails. > This occurs either when selecting File->Print... or File->Page Setup. > The full xemacs output is below. Confirm

RE: Xemacs print problem

On 14 November 2006 20:06, Eric Monsler wrote: > All, > > I have installed the xemacs as part of the cygwin setup. > > When trying to print from within xemacs, xemacs crashes and fails. > This occurs either when selecting File->Print... or File->Page Setup. > The full xemacs output is below. >

Re: Xemacs broken after postgresql upgrade

Dr. Volker Zell schrieb: Xemacs will be broken after upgrading postgresql to the new stable or test version. This is because Xemacs depends on pq.dll which somehow got renamed to cygpq.dll in newer versions of postgresql. I will rebuild Xemacs ASAP but can only upload in a week or so. In the mea

Re: Xemacs broken after postgresql upgrade

On Sun, Nov 13, 2005 at 03:53:36PM -0500, Charles Wilson wrote: > If that's the case, then (a) it's okay for Jason to package postgres > the way he does, It is up to Reini Urban, he is the PostgreSQL maintainer as of 8.x. Jason -- PGP/GPG Key: http://www.tishler.net/jason/pubkey.asc or key serv

Re: Xemacs broken after postgresql upgrade

On Sun, 13 Nov 2005, Brian Dessent wrote: > René Berber wrote: > > > A better fix is to link cygpq.dll to pq.dll: > > > > # ln /usr/bin/cygpq.dll /usr/bin/pq.dll > > That's not a great habit to get into. It will only work if the program > uses Cygwin methods (e.g. dlopen()) to dynamically load th

Re: Xemacs broken after postgresql upgrade

Brian Dessent wrote: René Berber wrote: A better fix is to link cygpq.dll to pq.dll: # ln /usr/bin/cygpq.dll /usr/bin/pq.dll that's a hardlink command, Brian -- which devolves to a copy on FAT32. That's not a great habit to get into. It will only work if the program uses Cygwin meth

Re: Xemacs broken after postgresql upgrade

Brian Dessent wrote: > René Berber wrote: > > >>A better fix is to link cygpq.dll to pq.dll: >> >># ln /usr/bin/cygpq.dll /usr/bin/pq.dll This will be hard link on WinNT+ and NTFS. So it will be ok for those with such configuration. > > > That's not a great habit to get into. It will only w

Re: Xemacs broken after postgresql upgrade

René Berber wrote: > A better fix is to link cygpq.dll to pq.dll: > > # ln /usr/bin/cygpq.dll /usr/bin/pq.dll That's not a great habit to get into. It will only work if the program uses Cygwin methods (e.g. dlopen()) to dynamically load the dll at runtime. It will absolutely not work for a .ex

Re: Xemacs broken after postgresql upgrade

Dr. Volker Zell wrote: > Xemacs will be broken after upgrading postgresql to the new stable or > test version. This is because Xemacs depends on pq.dll which somehow got > renamed to cygpq.dll in newer versions of postgresql. > > I will rebuild Xemacs ASAP but can only upload in a week or so. > I

Re: XEMACS and $HOME

> On Wed, 7 Sep 2005, Eric Blake wrote: > > > According to Achim Schaefer on 9/6/2005 7:50 AM: > > > Hi, > > > > > > I have a problem with my $HOME setting. > > > Starting xemacs I get the following message: > > > > > > $ xemacs > > > Syntax error: "Bad format environment-variable substitution", >

Re: XEMACS and $HOME

On Wed, 7 Sep 2005, Eric Blake wrote: > According to Achim Schaefer on 9/6/2005 7:50 AM: > > Hi, > > > > I have a problem with my $HOME setting. > > Starting xemacs I get the following message: > > > > $ xemacs > > Syntax error: "Bad format environment-variable substitution", > > "//SV018182/luxca

Re: XEMACS and $HOME

> According to Achim Schaefer on 9/6/2005 7:50 AM: > > Hi, > > > > I have a problem with my $HOME setting. > > Starting xemacs I get the following message: > > > > $ xemacs > > Syntax error: "Bad format environment-variable substitution", > > "//SV018182/luxcasch$" > > My only guess is that xem

Re: XEMACS and $HOME

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Achim Schaefer on 9/6/2005 7:50 AM: > Hi, > > I have a problem with my $HOME setting. > Starting xemacs I get the following message: > > $ xemacs > Syntax error: "Bad format environment-variable substitution", > "//SV018182/luxcasch$"

Re: XEmacs+aspell failed on cygwin 1.5.14-1

I'm happy to report that the latest snapshot fixed the XEmacs+Aspell problem. CGF, many thanks! I look forward to cygwin.1.5.15-1. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/doc

Re: XEmacs+aspell failed on cygwin 1.5.14-1

Christopher Faylor wrote: > On Tue, Apr 05, 2005 at 10:52:45AM -0400, [EMAIL PROTECTED] wrote: > >> The 2005-04-05 snapshot may fix this problem. It is being generated now. > > > >I just replaced /bin/cygwin1.dll (~1.2M) with the snapshot (more than 8M?). > > The DLL is reported as 1,944 Kb on t

Re: XEmacs+aspell failed on cygwin 1.5.14-1

On Tue, Apr 05, 2005 at 11:15:08AM -0400, TX wrote: >I left out some observations in my previous post. After I launch >XEmacs and click the "spell" button on the menu bar, the error message >box will immediately appear. If I click "OK" to terminate the program, >XEmacs hangs. I have to click to

Re: XEmacs+aspell failed on cygwin 1.5.14-1

On Tue, 5 Apr 2005, TX wrote: > Hi > This is what I did: 1) I close all cygwin apps. 2) I downloaded > cygwin1-20050405.dll.bz2 and unzip it. 3) I rename its unzipped version > to "cygwin1.dll". 4) I move this "cygwin1.dll" to "C:\cygwin\bin". > > Attached is the cygcheck.out. It reports the DLL a

RE: XEmacs+aspell failed on cygwin 1.5.14-1

Original Message >From: TX >Sent: 05 April 2005 16:43 > Hi > This is what I did: 1) I close all cygwin apps. 2) I downloaded > cygwin1-20050405.dll.bz2 and unzip it. 3) I rename its unzipped version to > "cygwin1.dll". 4) I move this "cygwin1.dll" to "C:\cygwin\bin". > > Attached is the c

Re: XEmacs+aspell failed on cygwin 1.5.14-1

Hi This is what I did: 1) I close all cygwin apps. 2) I downloaded cygwin1-20050405.dll.bz2 and unzip it. 3) I rename its unzipped version to "cygwin1.dll". 4) I move this "cygwin1.dll" to "C:\cygwin\bin". Attached is the cygcheck.out. It reports the DLL as 1.5.15 but cygwin (package) as 1.5.13-1.

RE: XEmacs+aspell failed on cygwin 1.5.14-1

Original Message >From: Christopher Faylor >Sent: 05 April 2005 16:28 > On Tue, Apr 05, 2005 at 04:10:52PM +0100, Dave Korn wrote: >>> On Tue, Apr 05, 2005 at 10:52:45AM -0400, xiet wrote: > The 2005-04-05 snapshot may fix this problem. It is being generated > now. I ju

Re: XEmacs+aspell failed on cygwin 1.5.14-1

On Tue, Apr 05, 2005 at 04:10:52PM +0100, Dave Korn wrote: >>On Tue, Apr 05, 2005 at 10:52:45AM -0400, xiet wrote: The 2005-04-05 snapshot may fix this problem. It is being generated now. >>> >>>I just replaced /bin/cygwin1.dll (~1.2M) with the snapshot (more than >>>8M?). >> >>The DLL is

Re: XEmacs+aspell failed on cygwin 1.5.14-1

Hi I left out some observations in my previous post. After I launch XEmacs and click the "spell" button on the menu bar, the error message box will immediately appear. If I click "OK" to terminate the program, XEmacs hangs. I have to click to close the XEmacs window. The normal Ctrl-XC won't work.

RE: XEmacs+aspell failed on cygwin 1.5.14-1

Original Message >From: Christopher Faylor >Sent: 05 April 2005 16:06 > On Tue, Apr 05, 2005 at 10:52:45AM -0400, xiet wrote: >>> The 2005-04-05 snapshot may fix this problem. It is being generated >>> now. >> >> I just replaced /bin/cygwin1.dll (~1.2M) with the snapshot (more than >> 8

Re: XEmacs+aspell failed on cygwin 1.5.14-1

On Tue, Apr 05, 2005 at 10:52:45AM -0400, [EMAIL PROTECTED] wrote: >> The 2005-04-05 snapshot may fix this problem. It is being generated now. > >I just replaced /bin/cygwin1.dll (~1.2M) with the snapshot (more than 8M?). The DLL is reported as 1,944 Kb on the web page. >cygcheck says the snapsh

Re: XEmacs+aspell failed on cygwin 1.5.14-1

On Mon, Apr 04, 2005 at 10:47:37PM -0400, TX wrote: >Sorry, I forgot to include the error message in my previous post: > >Aspell.exe - Application Error > >The instruction at "0x6109f478" referenced memory at "0x0010". >The memory could not be "read". The 2005-04-05 snapshot may fix this probl

Re: XEmacs+aspell failed on cygwin 1.5.14-1

TX wrote: Sorry, I forgot to include the error message in my previous post: Aspell.exe - Application Error The instruction at "0x6109f478" referenced memory at "0x0010". The memory could not be "read". Please help. Please read: Problem reports: http://cygwin.com/problems.html -- Jonathan

Re: XEmacs+aspell failed on cygwin 1.5.14-1

Sorry, I forgot to include the error message in my previous post: Aspell.exe - Application Error The instruction at "0x6109f478" referenced memory at "0x0010". The memory could not be "read". Please help. http://mysojourns.blogspot.com/ -- Unsubscribe info: http://cygwin.com/ml/#unsu

Re: XEmacs+aspell failed on cygwin 1.5.14-1

On Mon, Apr 04, 2005 at 10:34:27PM -0400, TX wrote: >Hi All >After installing the latest cygwin 1.5.14-1, I found myself unable to use >aspell within XEmacs. From the error message (about illegal memory >address?), I suspect that the problem is similar/related to other reported >memory-fault issues

Re: XEmacs and Windows Fonts

That's really too bad. I understood you maintained the cygwin version that gets installed with the cygwin netinstaller. With these font problems, that version is not usable if you do not run X. I had to revert to xemacs version 21.4.13 for cygwin as distributed through the xemacs.org netinstaller,

Re: XEmacs and Windows Fonts

> Jaap-Henk Hoepman writes: > I installed xemacs 21.4.15 yesterday (on cygwin 1.5.10-3) using the cygwin > netinstaller and still see the same problem (including weird truncation > characters, instead of the usual arrows i saw in previous versions, and > failure to redisplay p

Re: XEmacs and Windows Fonts

I installed xemacs 21.4.15 yesterday (on cygwin 1.5.10-3) using the cygwin netinstaller and still see the same problem (including weird truncation characters, instead of the usual arrows i saw in previous versions, and failure to redisplay properly). Regards, Jaap-Henk > > "David" == David

Re: xemacs shell problem

Some old XEmacs (21.1 era) was handling this correctly, so I believe the problem is in XEmacs. I haven't had a chance to trace XEmacs code yet. I have been using the following work around. None of which is perfect. 1) Stick with an old XEmacs. 2) Do run /usr/local/bin/xemacs. You can searc

Re: xemacs shell problem

Dave, As a beginner Xemacs-user with hardly any understanding of lisp (yet) I have to make sure that I understand it correctly. You suggest that I should, - Type "M-x eval-expression" - Type "(setq process-connection-type nil) [return]" - Observe that Minibuffer displays: "nil" - Type "M-x shell"

Re: xemacs shell problem

Igor Pechtchanski wrote: Cygwin uses special pipes, called "pty"s, for applications that aren't running in a console. I'm guessing that XEmacs uses these ptys for its shell buffer. It does by default, but this behavior can be changed by executing (setq process-connection-type nil) before startin

Re: xemacs shell problem

Thank you! Igor Pechtchanski wrote: Cygwin uses special pipes, called "pty"s, for applications that aren't running in a console. I'm guessing that XEmacs uses these ptys for its shell buffer. Some applications detect that they are not invoked from a console, and allocate one. If the application

Re: xemacs shell problem

On Fri, 14 May 2004, Levent Yilmaz wrote: > Hi! > > After posting this message to emacs.xemacs.windows and following the > advices I have been told, I found out that this happens only with Xemacs > Cygwin build. Thus, I hope it would be a relevant discussion for this > group. > > *the problem sett

Re: XEmacs 21.4.15, shell-mode not working?

> "Maarten" == Maarten Boekhold writes: Maarten> Hi all, Maarten> I just install the latest version of cygwin (downloaded last friday) on a new Maarten> computer, and I'm having a small problem with XEmacs (21.4.5). Maarten> It appears the shell-mode is not working. If I do '

Re: Xemacs Beta Build 21.5-b16

> "David" == David A Cobb writes: David> I tried to bring up the "beta" build of xemacs-21.5-b16 today and got David> a bit of a surprise. David> The "gamma" or mainline version: launching with $DISPLAY unset comes David> up using MS Windows - as advertised. David> The 21.

Re: XEmacs and hot laptops

> Most of laptops I've seen have fixed speed fans, that are turned on when > heat exceeds some predefined limit, and for some reasons on some laptops > fan just runs "for sure" once a while. > > Mine laptop is set as high as 70 celcius CPU temp, so well, it get's > hot, specially from under (Yes,

Re: XEmacs and hot laptops

[EMAIL PROTECTED] wrote: When I run cygwin XEmacs on my laptop after some time I have to close it as my laptop becomes very hot (and the fan goes non-stop and lot noisier than usual). So I work on porting some latex related stuff that works only on cygwin to native XEmacs. I wouldn't do that but

Re: XEmacs and hot laptops

Larry Hall wrote: Huh, I never noticed that before. I guess Eudora isn't as smart as I thought right out of the box. Well, I'll look into how to make it behave properly in all situations. As you can see from the below, it will choose the "human" name over the email address if it has the choi

Re: XEmacs and hot laptops

Huh, I never noticed that before. I guess Eudora isn't as smart as I thought right out of the box. Well, I'll look into how to make it behave properly in all situations. As you can see from the below, it will choose the "human" name over the email address if it has the choice (i.e. I didn't e

Re: XEmacs and hot laptops

Larry, Your email client is configured to quote raw e-mail addresses in replies, I think it would be good if you'd change that. Now my email address is visible for all spam harvesters to colect.. Greg Larry Hall wrote: At 12:49 AM 2/29/2004, borota you wrote: When I run cygwin XEmacs on my

Re: XEmacs and hot laptops

Yes it's true with the stuff I am doing xemacs uses the processor heavyly (according to task manager). Thanks, Greg Larry Hall wrote: At 12:49 AM 2/29/2004, [EMAIL PROTECTED] you wrote: When I run cygwin XEmacs on my laptop after some time I have to close it as my laptop becomes very hot (and t

Re: XEmacs and hot laptops

At 12:49 AM 2/29/2004, [EMAIL PROTECTED] you wrote: >When I run cygwin XEmacs on my laptop after some time I have to close it as my laptop >becomes very hot (and the fan goes non-stop and lot noisier than usual). So I work on >porting some latex related stuff that works only on cygwin to native X

RE: XEmacs-21.4.14-2 consistently crashes

>> "Thomas" == Thomas Demmer writes: > >Thomas> Until last week I was using 21.4.11 or so from xemacs.org, built with >Thomas> whatever cygwin they used and it ran fine, so I was assuming a cygwin bug >Thomas> here. > >In which mode does it run ? > >The following is copied from a he

Re: XEmacs-21.4.14-2 consistently crashes

> "Thomas" == Thomas Demmer writes: Thomas> Until last week I was using 21.4.11 or so from xemacs.org, built with Thomas> whatever cygwin they used and it ran fine, so I was assuming a cygwin bug Thomas> here. In which mode does it run ? The following is copied from a header file

RE: XEmacs-21.4.14-2 consistently crashes

> >> "Thomas" == Thomas Demmer writes: > >Thomas> Hi all, > >Hi Thomas, finally you send the message to the list :-) > >Thomas> I can reliably crash XEmacs by the following procedure: > >FWIW, me too. But since I will *never* use the Win32 version and have >never used the Win32 version

Re: XEmacs-21.4.14-2 consistently crashes

> "Thomas" == Thomas Demmer writes: Thomas> Hi all, Hi Thomas, finally you send the message to the list :-) Thomas> I can reliably crash XEmacs by the following procedure: FWIW, me too. But since I will *never* use the Win32 version and have never used the Win32 version as already s

Re: XEmacs and Windows Fonts

> "David" == David Rothenberger writes: David> Paul Stodghill wrote: >> I don't know if it is a 21.4.14 problem or a configuration problem. David> I believe it is a configuration problem of some sort. I am running a David> 21.4.14 that I built myself from CVS and did not enco

Re: XEmacs and Windows Fonts

Paul Stodghill wrote: I don't know if it is a 21.4.14 problem or a configuration problem. I believe it is a configuration problem of some sort. I am running a 21.4.14 that I built myself from CVS and did not encounter the problem with fonts. I'm also not seeing it with a 21.4.15 built from CVS.

Re: XEmacs and Windows Fonts

I observed this behavior with Cygwin's XEmacs too. I do not see this with Andy Piper's netinstall of 21.4.13 or 21.4.15, which I compiled from CVS myself. I don't know if it is a 21.4.14 problem or a configuration problem. When 21.4.15 for Cygwin is released, I will be in a better position to t

Re: XEmacs 21.4.14 appears to prevent W32 processes from exiting

> "Andre" == Andre Srinivasan writes: Andre> I noticed when I am running the Cygwin packaged version of XEmacs, Andre> programs like Opera, IE, etc never quite exit when I quit them Andre> (i.e. all windows close but process is still show in task manager); I Andre> need to go i

Re: Xemacs/cygwin 21.4.3 and new console window during compilation

-Original Message- >>From: [EMAIL PROTECTED] >>[mailto:[EMAIL PROTECTED]]On Behalf Of Larry Hall (RFK >>Partners, Inc) >>Sent: Tuesday, December 18, 2001 7:13 AM >>To: Dmitry Bely; Andy Piper >>Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] &

RE: Xemacs/cygwin 21.4.3 and new console window during compilation

[EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] > > Subject: Re: Xemacs/cygwin 21.4.3 and new console window during > > compilation > > > > > > At 03:11 AM 12/18/2001, Dmitry Bely wrote: > > >Andy Piper <[EMAIL PROTECTED]> writes: > > &

Re: Xemacs/cygwin 21.4.3 and new console window during compilation

At 03:11 AM 12/18/2001, Dmitry Bely wrote: >Andy Piper <[EMAIL PROTECTED]> writes: > > > So my supposition is that a console window is created because XEmacs > > doesn't have one by default when started from the desktop. > >Why then MSVC-compiled XEmacs does not popup new console in the same >situ

Re: Xemacs/cygwin 21.4.3 and new console window during compilation

Andy Piper <[EMAIL PROTECTED]> writes: > So my supposition is that a console window is created because XEmacs > doesn't have one by default when started from the desktop. Why then MSVC-compiled XEmacs does not popup new console in the same situation? It also seems not to have one by default ...

  1   2   >