Re: Fwd: aspell on XP
Paul A. Rubin wrote: Paul A. Rubin wrote: I finally got around to trying this on my home PC, which runs XP Home rather than XP Pro. Under XP Home, alt-F4 did *not* kill cmd.exe. On my laptop (XP Pro), it does. I haven't had a chance to try the XP Pro machine in my office (as I'm assiduously avoiding going anywhere near the office). My luck ran out and I ended up at the office. It turns out that alt-F4 does not kill either LyX or cmd.exe here (XP Pro). So my XP Pro laptop, where it does work, is apparently the outlier, although I have no explanation for why it works there. /Paul Using either a .lnk or a .pif doesn't change the inability to exit cmd.exe using alt-F4; I wonder if your laptop has an OEM modified installation of Win XP? I guess it is not likely, but the win98 default .pif file with more choices shows several keyboard shortcuts, but not alt-f4. But I think alt-f4 could be added to such a menu by a sourcerer, or even enabled as undocumented behavior without a menu. Must be a path with spaces problem ;-) Stephen
Re: Fwd: aspell on XP
Paul A. Rubin wrote: Paul A. Rubin wrote: I finally got around to trying this on my home PC, which runs XP Home rather than XP Pro. Under XP Home, alt-F4 did *not* kill cmd.exe. On my laptop (XP Pro), it does. I haven't had a chance to try the XP Pro machine in my office (as I'm assiduously avoiding going anywhere near the office). My luck ran out and I ended up at the office. It turns out that alt-F4 does not kill either LyX or cmd.exe here (XP Pro). So my XP Pro laptop, where it does work, is apparently the outlier, although I have no explanation for why it works there. /Paul I tried closing LyX with Alt-f4 with LyX1.4.1 and it didn't work, but with Joost's 1.4.2, closing with alt-f4 works if installed in either C:\LyXx or C:\Program Files\LyXx (path space), so it must be 'an obvious fact since those are the most deceptive.' -- Stephen Once you eliminate the impossible, whatever remains, no matter how improbable, must be the truth. SH: Sherlock Holmes (Doyle)
Re: Fwd: aspell on XP
Paul A. Rubin wrote: Paul A. Rubin wrote: I finally got around to trying this on my home PC, which runs XP Home rather than XP Pro. Under XP Home, alt-F4 did *not* kill cmd.exe. On my laptop (XP Pro), it does. I haven't had a chance to try the XP Pro machine in my office (as I'm assiduously avoiding going anywhere near the office). My luck ran out and I ended up at the office. It turns out that alt-F4 does not kill either LyX or cmd.exe here (XP Pro). So my XP Pro laptop, where it does work, is apparently the outlier, although I have no explanation for why it works there. /Paul Using either a .lnk or a .pif doesn't change the inability to exit cmd.exe using alt-F4; I wonder if your laptop has an OEM modified installation of Win XP? I guess it is not likely, but the win98 default .pif file with more choices shows several keyboard shortcuts, but not alt-f4. But I think alt-f4 could be added to such a menu by a sourcerer, or even enabled as undocumented behavior without a menu. Must be a path with spaces problem ;-) Stephen
Re: Fwd: aspell on XP
Paul A. Rubin wrote: Paul A. Rubin wrote: I finally got around to trying this on my home PC, which runs XP Home rather than XP Pro. Under XP Home, alt-F4 did *not* kill cmd.exe. On my laptop (XP Pro), it does. I haven't had a chance to try the XP Pro machine in my office (as I'm assiduously avoiding going anywhere near the office). My luck ran out and I ended up at the office. It turns out that alt-F4 does not kill either LyX or cmd.exe here (XP Pro). So my XP Pro laptop, where it does work, is apparently the outlier, although I have no explanation for why it works there. /Paul I tried closing LyX with Alt-f4 with LyX1.4.1 and it didn't work, but with Joost's 1.4.2, closing with alt-f4 works if installed in either C:\LyXx or C:\Program Files\LyXx (path space), so it must be 'an obvious fact since those are the most deceptive.' -- Stephen Once you eliminate the impossible, whatever remains, no matter how improbable, must be the truth. SH: Sherlock Holmes (Doyle)
Re: Fwd: aspell on XP
Paul A. Rubin wrote: Paul A. Rubin wrote: I finally got around to trying this on my home PC, which runs XP Home rather than XP Pro. Under XP Home, alt-F4 did *not* kill cmd.exe. On my laptop (XP Pro), it does. I haven't had a chance to try the XP Pro machine in my office (as I'm assiduously avoiding going anywhere near the office). My luck ran out and I ended up at the office. It turns out that alt-F4 does not kill either LyX or cmd.exe here (XP Pro). So my XP Pro laptop, where it does work, is apparently the outlier, although I have no explanation for why it works there. /Paul Using either a .lnk or a .pif doesn't change the inability to exit cmd.exe using alt-F4; I wonder if your laptop has an OEM modified installation of Win XP? I guess it is not likely, but the win98 default .pif file with more choices shows several keyboard shortcuts, but not alt-f4. But I think alt-f4 could be added to such a menu by a sourcerer, or even enabled as undocumented behavior without a menu. Must be a path with spaces problem ;-) Stephen
Re: Fwd: aspell on XP
Paul A. Rubin wrote: Paul A. Rubin wrote: I finally got around to trying this on my home PC, which runs XP Home rather than XP Pro. Under XP Home, alt-F4 did *not* kill cmd.exe. On my laptop (XP Pro), it does. I haven't had a chance to try the XP Pro machine in my office (as I'm assiduously avoiding going anywhere near the office). My luck ran out and I ended up at the office. It turns out that alt-F4 does not kill either LyX or cmd.exe here (XP Pro). So my XP Pro laptop, where it does work, is apparently the outlier, although I have no explanation for why it works there. /Paul I tried closing LyX with Alt-f4 with LyX1.4.1 and it didn't work, but with Joost's 1.4.2, closing with alt-f4 works if installed in either C:\LyXx or C:\Program Files\LyXx (path space), so it must be 'an obvious fact since those are the most deceptive.' -- Stephen "Once you eliminate the impossible, whatever remains, no matter how improbable, must be the truth." SH: Sherlock Holmes (Doyle)
Re: Fwd: aspell on XP
Paul A. Rubin wrote: Ed Gatzke wrote: So, cmd.exe and command.exe when started from Start-Run both do not respond to Alt-F4 for me either. Other things started from cmd.exe command prompt do listen to Alt F4 c:\windows\system32\winmine.exe and dvdplay.exe both respond to Alt-F4. I run most of my stuff from a cygwin shell, but everything closes on Alt-F4 except cmd.exe and lyx.exe. Even when I start lyx from the desktop shortcut, it does not respond to Alt-F4. Even when I double click on the cmd.exe in windows/system32 it does not respond to F4. I have tried cmd.exe on about 6 xp machines, Alt-F4 does nothing on any of them for cmd.exe. I finally got around to trying this on my home PC, which runs XP Home rather than XP Pro. Under XP Home, alt-F4 did *not* kill cmd.exe. On my laptop (XP Pro), it does. I haven't had a chance to try the XP Pro machine in my office (as I'm assiduously avoiding going anywhere near the office). The exact lyx installer is the most recent, the 2.0 installer for 1.41 lyxwininstall/LyxWin141Complete-2.01.exe Even just running lyx.exe (not lyx.bat) appears to open a shell for a second before the application launches... Very odd, I wonder what is up. Maybe the shell is the root of all problems with Alt-F4. I'm not sure what goes on in that fleeting shell, but according to the task manager I use, when you run lyx.exe directly it is not running in a shell. LyX does, however, make extensive use of shell scripts (for converting graphics, running the configuration script, etc.), so it may be running some quick script at that point. This stuff is crazy. I tried posting on some MS help pages, and the MS experts suggested I use Alt-Space then C, which breaks the standard that Alt-F4 closes everything, like hitting the big red X. I agree it's strange, but as far back as I can remember, Microsoft's insistence that third-party developers adhere to their rules for Windows programs has not extended to their own programmers. Nor have they been philosophically consistent. Thus Windows 3.x came with an FTP client that had a GUI, but Windows 95/98 et seq. come only with a DOS FTP client -- even though Microsoft has been trying to phase out DOS in the last few iterations of Windows. I'm quite curious why you and Steve and I get three different behavior patterns from ostensibly the same OS. (I'm assuming that you and Steve are both using XP Pro, fully patched.) /Paul No, I think Ed mentioned he used Cygwin. Luckily, Enrico tutored me (everything beautiful belongs to Enrico and the ugly is all mine). When Ed starts LyX from a cygwin shell the batfile he is using leaves the (bash) shell open as a hanging process. I had that problem too and I wanted the X-server (the one in a white window,xterm) to close so that I could use it to open another program besides LyX. I mean it spawns lyx and then returns to being available separately. So I sort of fixed it. I'll put the lyx11.bat text at the end. I used some other file as a basis (startxwin.bat) and mostly just tacked on run c:\cygwin\usr\local\bin\lyx-x11.exe: at the end. I start it with a desktop icon: target C:\cygwin\usr\X11R6\bin\LyX11.bat start in C:\cygwin\usr\X11R6\bin I can create the problem if I start *native* LyX from the cygwin shell, then it opens a black/bash window that won't close. Otherwise I can close both the shell and lyx using alt-f4. It works ok to open from cmd.exe shell, lyx with either lyx.bat or lyx.exe and then close with alt-f4. I researched and found a few reports complaining about not being able to close cmd.exe with alt-f4. I found no report of being able to close cmd.exe shell with alt-f4. I think Paul has a very talented machine. I don't think it is meant or built to close under native Windows, so use exit return if you don't want to use the mouse. I think if you are using cygwin to open native windows lyx rather than cygwin lyx, you could modify the startxwin.bat to lyx11.bat and point it to run C:\lyx142\LyX14\bin\lyx11.bat (modify appropriately) and start in: C:\lyx142\LyX14\bin (desktop icon) rather than C:\cygwin\usr\X11R6\bin\LyX11.bat the last line in startxwin.bat changed to lyx11.bat would change run c:\cygwin\usr\local\bin\lyx-x11.exe and would change to run C:\lyx142\LyX14\bin\lyx.bat or lyx.exe not lyx-x11.exe I mean that I can start native LyX from an xterm window, with two separate windows that each close with alt-f4. Incidentally, the cygwin version of lyx1.4.1 runs on Windows 98 Re: Installing LyX on Windows 98 - Solved fairly well with Cygwin Cheers, Stephen -- cut and paste lyx11.bat @echo off SET DISPLAY=127.0.0.1:0.0 REM REM The path in the CYGWIN_ROOT environment variable assignment assume REM that Cygwin is installed in a directory called 'cygwin' in the root REM directory of the current drive. You will only need to modify REM CYGWIN_ROOT if you have installed Cygwin in
Re: Fwd: aspell on XP
Ed Gatzke wrote: I have tried cmd.exe on about 6 xp machines, Alt-F4 does nothing on any of them for cmd.exe. I finally got around to trying this on my home PC, which runs XP Home rather than XP Pro. Under XP Home, alt-F4 did *not* kill cmd.exe. On my laptop (XP Pro), it does. I haven't had a chance to try the XP Pro machine in my office (as I'm assiduously avoiding Some of the machines I tried to kill cmd.exe on were NOT XP home ( My new work desktop and my wifes work laptop). I'm not sure what goes on in that fleeting shell, but according to the task manager I use, when you run lyx.exe directly it is not running in a shell. LyX does, however, make extensive use of shell scripts (for converting graphics, running the configuration script, etc.), so it may be running some quick script at that point. There is a python.exe file in the same directory as the lyx.exe executable. Python opens what looks like a cmd.exe window that you can't close with Alt-F4 either. I wonder if lyx.exe is somehow running in a python shell? No, I think Ed mentioned he used Cygwin. Luckily, Enrico tutored me (everything beautiful belongs to Enrico and the ugly is all mine). I have tried starting LyX all different ways, from the cygwin shell, from the desktop icon, from the bat file in Program Files / lyx, from the exe file in Program Files / LyX. None of those close with Alt-F4, but I will try the bat file hacks below. So I sort of fixed it. I'll put the lyx11.bat text at the end. I used some other file as a basis (startxwin.bat) and mostly just tacked on run c:\cygwin\usr\local\bin\lyx-x11.exe: at the end. I start it with a desktop icon: target C:\cygwin\usr\X11R6\bin\LyX11.bat start in C:\cygwin\usr\X11R6\bin Thanks for all your help trying to sort this out. I think if you have X11 and xterm working this will work. The problem can be duplicated here using the black/bash shell. The AutoHotkeys will work on cmd.exe and some windows apps but if LyX is started from Cygwin closing it still requires alt-f4 (with a modified startxwin.bat) on my system. It seems odd. Regards, Stephen
Re: Fwd: aspell on XP
Ed Gatzke wrote: There is a python.exe file in the same directory as the lyx.exe executable. Python opens what looks like a cmd.exe window that you can't close with Alt-F4 either. I wonder if lyx.exe is somehow running in a python shell? No. LyX runs Python scripts for various things, but LyX itself is not written in Python (nor started by a Python script). On my laptop, alt-F4 kills Python windows. /Paul
Re: Fwd: aspell on XP
Ed Gatzke wrote: This stuff is crazy. I tried posting on some MS help pages, and the MS experts suggested I use Alt-Space then C, which breaks the standard that Alt-F4 closes everything, like hitting the big red X. I found a workaround. http://www.autohotkey.com/download/ AutoHotKey is a free download that makes use of the Windows key in conjunction with another letter. So you start AutoHotKey (I made a desktop shortcut)and when the Windows key is pressed with the k (for kill) key the active program will close if it's cmd.exe or another app. (repeats). Stays resident until you close it or shutdown. Win-key with k-key Sends the keystrokes: alt, space, Shift C to make a capital C. #k::send ! +C cut and paste into the kill.ahk file; I read the quick tutorial. Regards, Stephen
Re: Fwd: aspell on XP
Steve Harris wrote: I researched and found a few reports complaining about not being able to close cmd.exe with alt-f4. I found no report of being able to close cmd.exe shell with alt-f4. I think Paul has a very talented machine. Boy, you sure wouldn't know it from its general performance! :-) I don't think it is meant or built to close under native Windows, so use exit return if you don't want to use the mouse. Back in the Windows 9x era, I'm pretty sure that a command window was designed not to be too easily killed (presumably lest one lose work, possibly lest one leave an orphan process around), so I would not be surprised if alt-F4 did not kill it. If you clicked the X (close) box in the upper right, you got a stern warning that something dire might happen if you really closed it that way. I haven't seen that warning in XP Pro, and if you can kill the shell with the X box, no reason why alt-F4 shouldn't do so as well. /Paul
Re: Fwd: aspell on XP
Paul A. Rubin wrote: Steve Harris wrote: Back in the Windows 9x era, I'm pretty sure that a command window was designed not to be too easily killed (presumably lest one lose work, possibly lest one leave an orphan process around), so I would not be surprised if alt-F4 did not kill it. If you clicked the X (close) box in the upper right, you got a stern warning that something dire might happen if you really closed it that way. I haven't seen that warning in XP Pro, and if you can kill the shell with the X box, no reason why alt-F4 shouldn't do so as well. /Paul Well, does the nag come from a .lnk or a .pif? #40 http://www.bootstrike.com/WinXP/faq.html#40 ... Furthermore, it turns out that there are TWO ways to run CMD.EXE in Windows XP, although this fact is not documented anywhere. CMD.EXE can be run from a shortcut (a .lnk file, which is the way that the Command Prompt window is set up out-of-the-box in Windows XP) or from a Program Information File (a .pif file). (COMMAND.COM, on the other hand, can ONLY be run from a .pif file, since it is a .com program and not a .exe program.) I have found the .pif file method for running CMD.EXE to be superior in most respects. For one thing, the .pif file Properties dialog gives you control of a lot more of the compatibility options. More importantly, however, most of my DOS applications simply run better when CMD.EXE is invoked by a .pif file. The most visible difference is in the colors within the Command Prompt window. My favorite DOS-based source code editor, for example, displays with a hideous green background color when run under a CMD.EXE shortcut, but runs correctly (with a black background) when run under CMD.EXE invoked via a .pif file. The DOS full-screen edit command has similar problems with colors when run under a shortcut, but again runs correctly under a .pif file. There are two minor annoyances, however, when running CMD.EXE from a .pif file: * Any switches that you specify in the dir command (such as /w) are ignored. The dir command uses ONLY the options you have set in the environment via the DIRCMD variable. * If you are sitting at a command prompt, not running a command or application, and you try to terminate the window by clicking the X box in the upper right-hand corner of the window frame, you get a nag dialog. The exit command does work correctly, without the nag. SH: I suspect this change of behavior from Win9x to XP Pro is due to an out-of-the-box OEM .lnk file, rather than a spiffy .pif file. After doing about 3 hours of research on this, I couldn't resist Sharing the wealth of knowledge :-) Stephen
Re: Fwd: aspell on XP
Paul A. Rubin wrote: Ed Gatzke wrote: So, cmd.exe and command.exe when started from Start-Run both do not respond to Alt-F4 for me either. Other things started from cmd.exe command prompt do listen to Alt F4 c:\windows\system32\winmine.exe and dvdplay.exe both respond to Alt-F4. I run most of my stuff from a cygwin shell, but everything closes on Alt-F4 except cmd.exe and lyx.exe. Even when I start lyx from the desktop shortcut, it does not respond to Alt-F4. Even when I double click on the cmd.exe in windows/system32 it does not respond to F4. I have tried cmd.exe on about 6 xp machines, Alt-F4 does nothing on any of them for cmd.exe. I finally got around to trying this on my home PC, which runs XP Home rather than XP Pro. Under XP Home, alt-F4 did *not* kill cmd.exe. On my laptop (XP Pro), it does. I haven't had a chance to try the XP Pro machine in my office (as I'm assiduously avoiding going anywhere near the office). The exact lyx installer is the most recent, the 2.0 installer for 1.41 lyxwininstall/LyxWin141Complete-2.01.exe Even just running lyx.exe (not lyx.bat) appears to open a shell for a second before the application launches... Very odd, I wonder what is up. Maybe the shell is the root of all problems with Alt-F4. I'm not sure what goes on in that fleeting shell, but according to the task manager I use, when you run lyx.exe directly it is not running in a shell. LyX does, however, make extensive use of shell scripts (for converting graphics, running the configuration script, etc.), so it may be running some quick script at that point. This stuff is crazy. I tried posting on some MS help pages, and the MS experts suggested I use Alt-Space then C, which breaks the standard that Alt-F4 closes everything, like hitting the big red X. I agree it's strange, but as far back as I can remember, Microsoft's insistence that third-party developers adhere to their rules for Windows programs has not extended to their own programmers. Nor have they been philosophically consistent. Thus Windows 3.x came with an FTP client that had a GUI, but Windows 95/98 et seq. come only with a DOS FTP client -- even though Microsoft has been trying to phase out DOS in the last few iterations of Windows. I'm quite curious why you and Steve and I get three different behavior patterns from ostensibly the same OS. (I'm assuming that you and Steve are both using XP Pro, fully patched.) /Paul No, I think Ed mentioned he used Cygwin. Luckily, Enrico tutored me (everything beautiful belongs to Enrico and the ugly is all mine). When Ed starts LyX from a cygwin shell the batfile he is using leaves the (bash) shell open as a hanging process. I had that problem too and I wanted the X-server (the one in a white window,xterm) to close so that I could use it to open another program besides LyX. I mean it spawns lyx and then returns to being available separately. So I sort of fixed it. I'll put the lyx11.bat text at the end. I used some other file as a basis (startxwin.bat) and mostly just tacked on run c:\cygwin\usr\local\bin\lyx-x11.exe: at the end. I start it with a desktop icon: target C:\cygwin\usr\X11R6\bin\LyX11.bat start in C:\cygwin\usr\X11R6\bin I can create the problem if I start *native* LyX from the cygwin shell, then it opens a black/bash window that won't close. Otherwise I can close both the shell and lyx using alt-f4. It works ok to open from cmd.exe shell, lyx with either lyx.bat or lyx.exe and then close with alt-f4. I researched and found a few reports complaining about not being able to close cmd.exe with alt-f4. I found no report of being able to close cmd.exe shell with alt-f4. I think Paul has a very talented machine. I don't think it is meant or built to close under native Windows, so use exit return if you don't want to use the mouse. I think if you are using cygwin to open native windows lyx rather than cygwin lyx, you could modify the startxwin.bat to lyx11.bat and point it to run C:\lyx142\LyX14\bin\lyx11.bat (modify appropriately) and start in: C:\lyx142\LyX14\bin (desktop icon) rather than C:\cygwin\usr\X11R6\bin\LyX11.bat the last line in startxwin.bat changed to lyx11.bat would change run c:\cygwin\usr\local\bin\lyx-x11.exe and would change to run C:\lyx142\LyX14\bin\lyx.bat or lyx.exe not lyx-x11.exe I mean that I can start native LyX from an xterm window, with two separate windows that each close with alt-f4. Incidentally, the cygwin version of lyx1.4.1 runs on Windows 98 Re: Installing LyX on Windows 98 - Solved fairly well with Cygwin Cheers, Stephen -- cut and paste lyx11.bat @echo off SET DISPLAY=127.0.0.1:0.0 REM REM The path in the CYGWIN_ROOT environment variable assignment assume REM that Cygwin is installed in a directory called 'cygwin' in the root REM directory of the current drive. You will only need to modify REM CYGWIN_ROOT if you have installed Cygwin in
Re: Fwd: aspell on XP
Ed Gatzke wrote: I have tried cmd.exe on about 6 xp machines, Alt-F4 does nothing on any of them for cmd.exe. I finally got around to trying this on my home PC, which runs XP Home rather than XP Pro. Under XP Home, alt-F4 did *not* kill cmd.exe. On my laptop (XP Pro), it does. I haven't had a chance to try the XP Pro machine in my office (as I'm assiduously avoiding Some of the machines I tried to kill cmd.exe on were NOT XP home ( My new work desktop and my wifes work laptop). I'm not sure what goes on in that fleeting shell, but according to the task manager I use, when you run lyx.exe directly it is not running in a shell. LyX does, however, make extensive use of shell scripts (for converting graphics, running the configuration script, etc.), so it may be running some quick script at that point. There is a python.exe file in the same directory as the lyx.exe executable. Python opens what looks like a cmd.exe window that you can't close with Alt-F4 either. I wonder if lyx.exe is somehow running in a python shell? No, I think Ed mentioned he used Cygwin. Luckily, Enrico tutored me (everything beautiful belongs to Enrico and the ugly is all mine). I have tried starting LyX all different ways, from the cygwin shell, from the desktop icon, from the bat file in Program Files / lyx, from the exe file in Program Files / LyX. None of those close with Alt-F4, but I will try the bat file hacks below. So I sort of fixed it. I'll put the lyx11.bat text at the end. I used some other file as a basis (startxwin.bat) and mostly just tacked on run c:\cygwin\usr\local\bin\lyx-x11.exe: at the end. I start it with a desktop icon: target C:\cygwin\usr\X11R6\bin\LyX11.bat start in C:\cygwin\usr\X11R6\bin Thanks for all your help trying to sort this out. I think if you have X11 and xterm working this will work. The problem can be duplicated here using the black/bash shell. The AutoHotkeys will work on cmd.exe and some windows apps but if LyX is started from Cygwin closing it still requires alt-f4 (with a modified startxwin.bat) on my system. It seems odd. Regards, Stephen
Re: Fwd: aspell on XP
Ed Gatzke wrote: There is a python.exe file in the same directory as the lyx.exe executable. Python opens what looks like a cmd.exe window that you can't close with Alt-F4 either. I wonder if lyx.exe is somehow running in a python shell? No. LyX runs Python scripts for various things, but LyX itself is not written in Python (nor started by a Python script). On my laptop, alt-F4 kills Python windows. /Paul
Re: Fwd: aspell on XP
Ed Gatzke wrote: This stuff is crazy. I tried posting on some MS help pages, and the MS experts suggested I use Alt-Space then C, which breaks the standard that Alt-F4 closes everything, like hitting the big red X. I found a workaround. http://www.autohotkey.com/download/ AutoHotKey is a free download that makes use of the Windows key in conjunction with another letter. So you start AutoHotKey (I made a desktop shortcut)and when the Windows key is pressed with the k (for kill) key the active program will close if it's cmd.exe or another app. (repeats). Stays resident until you close it or shutdown. Win-key with k-key Sends the keystrokes: alt, space, Shift C to make a capital C. #k::send ! +C cut and paste into the kill.ahk file; I read the quick tutorial. Regards, Stephen
Re: Fwd: aspell on XP
Steve Harris wrote: I researched and found a few reports complaining about not being able to close cmd.exe with alt-f4. I found no report of being able to close cmd.exe shell with alt-f4. I think Paul has a very talented machine. Boy, you sure wouldn't know it from its general performance! :-) I don't think it is meant or built to close under native Windows, so use exit return if you don't want to use the mouse. Back in the Windows 9x era, I'm pretty sure that a command window was designed not to be too easily killed (presumably lest one lose work, possibly lest one leave an orphan process around), so I would not be surprised if alt-F4 did not kill it. If you clicked the X (close) box in the upper right, you got a stern warning that something dire might happen if you really closed it that way. I haven't seen that warning in XP Pro, and if you can kill the shell with the X box, no reason why alt-F4 shouldn't do so as well. /Paul
Re: Fwd: aspell on XP
Paul A. Rubin wrote: Steve Harris wrote: Back in the Windows 9x era, I'm pretty sure that a command window was designed not to be too easily killed (presumably lest one lose work, possibly lest one leave an orphan process around), so I would not be surprised if alt-F4 did not kill it. If you clicked the X (close) box in the upper right, you got a stern warning that something dire might happen if you really closed it that way. I haven't seen that warning in XP Pro, and if you can kill the shell with the X box, no reason why alt-F4 shouldn't do so as well. /Paul Well, does the nag come from a .lnk or a .pif? #40 http://www.bootstrike.com/WinXP/faq.html#40 ... Furthermore, it turns out that there are TWO ways to run CMD.EXE in Windows XP, although this fact is not documented anywhere. CMD.EXE can be run from a shortcut (a .lnk file, which is the way that the Command Prompt window is set up out-of-the-box in Windows XP) or from a Program Information File (a .pif file). (COMMAND.COM, on the other hand, can ONLY be run from a .pif file, since it is a .com program and not a .exe program.) I have found the .pif file method for running CMD.EXE to be superior in most respects. For one thing, the .pif file Properties dialog gives you control of a lot more of the compatibility options. More importantly, however, most of my DOS applications simply run better when CMD.EXE is invoked by a .pif file. The most visible difference is in the colors within the Command Prompt window. My favorite DOS-based source code editor, for example, displays with a hideous green background color when run under a CMD.EXE shortcut, but runs correctly (with a black background) when run under CMD.EXE invoked via a .pif file. The DOS full-screen edit command has similar problems with colors when run under a shortcut, but again runs correctly under a .pif file. There are two minor annoyances, however, when running CMD.EXE from a .pif file: * Any switches that you specify in the dir command (such as /w) are ignored. The dir command uses ONLY the options you have set in the environment via the DIRCMD variable. * If you are sitting at a command prompt, not running a command or application, and you try to terminate the window by clicking the X box in the upper right-hand corner of the window frame, you get a nag dialog. The exit command does work correctly, without the nag. SH: I suspect this change of behavior from Win9x to XP Pro is due to an out-of-the-box OEM .lnk file, rather than a spiffy .pif file. After doing about 3 hours of research on this, I couldn't resist Sharing the wealth of knowledge :-) Stephen
Re: Fwd: aspell on XP
Paul A. Rubin wrote: Ed Gatzke wrote: So, cmd.exe and command.exe when started from Start->Run both do not respond to Alt-F4 for me either. Other things started from cmd.exe command prompt do listen to Alt F4 c:\windows\system32\winmine.exe and dvdplay.exe both respond to Alt-F4. I run most of my stuff from a cygwin shell, but everything closes on Alt-F4 except cmd.exe and lyx.exe. Even when I start lyx from the desktop shortcut, it does not respond to Alt-F4. Even when I double click on the cmd.exe in windows/system32 it does not respond to F4. I have tried cmd.exe on about 6 xp machines, Alt-F4 does nothing on any of them for cmd.exe. I finally got around to trying this on my home PC, which runs XP Home rather than XP Pro. Under XP Home, alt-F4 did *not* kill cmd.exe. On my laptop (XP Pro), it does. I haven't had a chance to try the XP Pro machine in my office (as I'm assiduously avoiding going anywhere near the office). The exact lyx installer is the most recent, the 2.0 installer for 1.41 lyxwininstall/LyxWin141Complete-2.01.exe Even just running lyx.exe (not lyx.bat) appears to open a shell for a second before the application launches... Very odd, I wonder what is up. Maybe the shell is the root of all problems with Alt-F4. I'm not sure what goes on in that fleeting shell, but according to the task manager I use, when you run lyx.exe directly it is not running in a shell. LyX does, however, make extensive use of shell scripts (for converting graphics, running the configuration script, etc.), so it may be running some quick script at that point. This stuff is crazy. I tried posting on some MS "help" pages, and the "MS experts" suggested I use Alt-Space then C, which breaks the standard that Alt-F4 closes everything, like hitting the big red X. I agree it's strange, but as far back as I can remember, Microsoft's insistence that third-party developers adhere to their rules for Windows programs has not extended to their own programmers. Nor have they been philosophically consistent. Thus Windows 3.x came with an FTP client that had a GUI, but Windows 95/98 et seq. come only with a DOS FTP client -- even though Microsoft has been trying to phase out DOS in the last few iterations of Windows. I'm quite curious why you and Steve and I get three different behavior patterns from ostensibly the same OS. (I'm assuming that you and Steve are both using XP Pro, fully patched.) /Paul No, I think Ed mentioned he used Cygwin. Luckily, Enrico tutored me (everything beautiful belongs to Enrico and the ugly is all mine). When Ed starts LyX from a cygwin shell the batfile he is using leaves the (bash) shell open as a hanging process. I had that problem too and I wanted the X-server (the one in a white window,xterm) to close so that I could use it to open another program besides LyX. I mean it spawns lyx and then returns to being available separately. So I sort of fixed it. I'll put the lyx11.bat text at the end. I used some other file as a basis (startxwin.bat) and mostly just tacked on "run c:\cygwin\usr\local\bin\lyx-x11.exe: at the end. I start it with a desktop icon: target C:\cygwin\usr\X11R6\bin\LyX11.bat start in C:\cygwin\usr\X11R6\bin I can create the problem if I start *native* LyX from the cygwin shell, then it opens a black/bash window that won't close. Otherwise I can close both the shell and lyx using alt-f4. It works ok to open from cmd.exe shell, lyx with either lyx.bat or lyx.exe and then close with alt-f4. I researched and found a few reports complaining about not being able to close cmd.exe with alt-f4. I found no report of being able to close cmd.exe shell with alt-f4. I think Paul has a very talented machine. I don't think it is meant or built to close under native Windows, so use "exit" if you don't want to use the mouse. I think if you are using cygwin to open native windows lyx rather than cygwin lyx, you could modify the startxwin.bat to lyx11.bat and point it to "run C:\lyx142\LyX14\bin\lyx11.bat" (modify appropriately) and start in: C:\lyx142\LyX14\bin (desktop icon) rather than C:\cygwin\usr\X11R6\bin\LyX11.bat the last line in startxwin.bat changed to lyx11.bat would change "run c:\cygwin\usr\local\bin\lyx-x11.exe" and would change to "run C:\lyx142\LyX14\bin\lyx.bat or lyx.exe not lyx-x11.exe I mean that I can start native LyX from an xterm window, with two separate windows that each close with alt-f4. Incidentally, the cygwin version of lyx1.4.1 runs on Windows 98 "Re: Installing LyX on Windows 98 - Solved fairly well with Cygwin" Cheers, Stephen -- cut and paste lyx11.bat @echo off SET DISPLAY=127.0.0.1:0.0 REM REM The path in the CYGWIN_ROOT environment variable assignment assume REM that Cygwin is installed in a directory called 'cygwin' in the root REM directory of the current drive. You will only need to modify REM CYGWIN_ROOT if you have installed Cygwin
Re: Fwd: aspell on XP
Ed Gatzke wrote: I have tried cmd.exe on about 6 xp machines, Alt-F4 does nothing on any of them for cmd.exe. I finally got around to trying this on my home PC, which runs XP Home rather than XP Pro. Under XP Home, alt-F4 did *not* kill cmd.exe. On my laptop (XP Pro), it does. I haven't had a chance to try the XP Pro machine in my office (as I'm assiduously avoiding Some of the machines I tried to kill cmd.exe on were NOT XP home ( My new work desktop and my wifes work laptop). I'm not sure what goes on in that fleeting shell, but according to the task manager I use, when you run lyx.exe directly it is not running in a shell. LyX does, however, make extensive use of shell scripts (for converting graphics, running the configuration script, etc.), so it may be running some quick script at that point. There is a python.exe file in the same directory as the lyx.exe executable. Python opens what looks like a cmd.exe window that you can't close with Alt-F4 either. I wonder if lyx.exe is somehow running in a python shell? No, I think Ed mentioned he used Cygwin. Luckily, Enrico tutored me (everything beautiful belongs to Enrico and the ugly is all mine). I have tried starting LyX all different ways, from the cygwin shell, from the desktop icon, from the bat file in Program Files / lyx, from the exe file in Program Files / LyX. None of those close with Alt-F4, but I will try the bat file hacks below. So I sort of fixed it. I'll put the lyx11.bat text at the end. I used some other file as a basis (startxwin.bat) and mostly just tacked on "run c:\cygwin\usr\local\bin\lyx-x11.exe: at the end. I start it with a desktop icon: target C:\cygwin\usr\X11R6\bin\LyX11.bat start in C:\cygwin\usr\X11R6\bin Thanks for all your help trying to sort this out. I think if you have X11 and xterm working this will work. The problem can be duplicated here using the black/bash shell. The AutoHotkeys will work on cmd.exe and some windows apps but if LyX is started from Cygwin closing it still requires alt-f4 (with a modified startxwin.bat) on my system. It seems odd. Regards, Stephen
Re: Fwd: aspell on XP
Ed Gatzke wrote: There is a python.exe file in the same directory as the lyx.exe executable. Python opens what looks like a cmd.exe window that you can't close with Alt-F4 either. I wonder if lyx.exe is somehow running in a python shell? No. LyX runs Python scripts for various things, but LyX itself is not written in Python (nor started by a Python script). On my laptop, alt-F4 kills Python windows. /Paul
Re: Fwd: aspell on XP
Ed Gatzke wrote: This stuff is crazy. I tried posting on some MS "help" pages, and the "MS experts" suggested I use Alt-Space then C, which breaks the standard that Alt-F4 closes everything, like hitting the big red X. I found a workaround. http://www.autohotkey.com/download/ AutoHotKey is a free download that makes use of the Windows key in conjunction with another letter. So you start AutoHotKey (I made a desktop shortcut)and when the Windows key is pressed with the k (for kill) key the active program will close if it's cmd.exe or another app. (repeats). Stays resident until you close it or shutdown. Win-key with k-key Sends the keystrokes: alt, space, Shift C to make a capital C. #k::send ! +C cut and paste into the kill.ahk file; I read the quick tutorial. Regards, Stephen
Re: Fwd: aspell on XP
Steve Harris wrote: I researched and found a few reports complaining about not being able to close cmd.exe with alt-f4. I found no report of being able to close cmd.exe shell with alt-f4. I think Paul has a very talented machine. Boy, you sure wouldn't know it from its general performance! :-) I don't think it is meant or built to close under native Windows, so use "exit" if you don't want to use the mouse. Back in the Windows 9x era, I'm pretty sure that a command window was designed not to be too easily killed (presumably lest one lose work, possibly lest one leave an orphan process around), so I would not be surprised if alt-F4 did not kill it. If you clicked the X (close) box in the upper right, you got a stern warning that something dire might happen if you really closed it that way. I haven't seen that warning in XP Pro, and if you can kill the shell with the X box, no reason why alt-F4 shouldn't do so as well. /Paul
Re: Fwd: aspell on XP
Paul A. Rubin wrote: Steve Harris wrote: Back in the Windows 9x era, I'm pretty sure that a command window was designed not to be too easily killed (presumably lest one lose work, possibly lest one leave an orphan process around), so I would not be surprised if alt-F4 did not kill it. If you clicked the X (close) box in the upper right, you got a stern warning that something dire might happen if you really closed it that way. I haven't seen that warning in XP Pro, and if you can kill the shell with the X box, no reason why alt-F4 shouldn't do so as well. /Paul Well, does the nag come from a .lnk or a .pif? #40 http://www.bootstrike.com/WinXP/faq.html#40 ... "Furthermore, it turns out that there are TWO ways to run CMD.EXE in Windows XP, although this fact is not documented anywhere. CMD.EXE can be run from a shortcut (a .lnk file, which is the way that the Command Prompt window is set up "out-of-the-box" in Windows XP) or from a Program Information File (a .pif file). (COMMAND.COM, on the other hand, can ONLY be run from a .pif file, since it is a .com program and not a .exe program.) I have found the .pif file method for running CMD.EXE to be superior in most respects. For one thing, the .pif file "Properties" dialog gives you control of a lot more of the "compatibility" options. More importantly, however, most of my DOS applications simply run better when CMD.EXE is invoked by a .pif file. The most visible difference is in the colors within the Command Prompt window. My favorite DOS-based source code editor, for example, displays with a hideous green background color when run under a CMD.EXE shortcut, but runs correctly (with a black background) when run under CMD.EXE invoked via a .pif file. The DOS full-screen "edit" command has similar problems with colors when run under a shortcut, but again runs correctly under a .pif file. There are two minor annoyances, however, when running CMD.EXE from a .pif file: * Any switches that you specify in the "dir" command (such as "/w") are ignored. The "dir" command uses ONLY the options you have set in the environment via the "DIRCMD" variable. * If you are sitting at a command prompt, not running a command or application, and you try to terminate the window by clicking the "X" box in the upper right-hand corner of the window frame, you get a "nag" dialog. The "exit" command does work correctly, without the nag." SH: I suspect this change of behavior from Win9x to XP Pro is due to an out-of-the-box OEM .lnk file, rather than a spiffy .pif file. After doing about 3 hours of research on this, I couldn't resist Sharing the wealth of knowledge :-) Stephen
Re: Fwd: aspell on XP
Steve Harris [EMAIL PROTECTED] writes: Paul A. Rubin wrote: Steve Harris wrote: I have LyX 1.4.2 installed and alt-f4 kills lyx but not cmd.exe My keyboard requires using an F-lock key to enable standard features. Hmm. I was going to ask John and Ed whether alt-F4 kills programs other than LyX that are being run in shells (rather than as native Windows apps) (if I'm expressing that distinction correctly). My suspicion was that maybe failure to kill cmd.exe implied inability to kill anything running in a shell. However, if alt-F4 kills LyX and not cmd.exe for So, cmd.exe and command.exe when started from Start-Run both do not respond to Alt-F4 for me either. Other things started from cmd.exe command prompt do listen to Alt F4 c:\windows\system32\winmine.exe and dvdplay.exe both respond to Alt-F4. I run most of my stuff from a cygwin shell, but everything closes on Alt-F4 except cmd.exe and lyx.exe. Even when I start lyx from the desktop shortcut, it does not respond to Alt-F4. Even when I double click on the cmd.exe in windows/system32 it does not respond to F4. I have tried cmd.exe on about 6 xp machines, Alt-F4 does nothing on any of them for cmd.exe. The exact lyx installer is the most recent, the 2.0 installer for 1.41 lyxwininstall/LyxWin141Complete-2.01.exe Even just running lyx.exe (not lyx.bat) appears to open a shell for a second before the application launches... Very odd, I wonder what is up. Maybe the shell is the root of all problems with Alt-F4. That is actually quite a good theory...because there are different versions of installers and the original port might not have had a hook(?) built into it. But it wouldn't explain a difference in behavior at an OS level, methinks. I just tried Alt-F4 on my Win98 machine Dos-prompt and that doesn't affect it. I thought perhaps your system might have had an earlier compatibility mode enabled, which would produce a different result. I'll look into it. This stuff is crazy. I tried posting on some MS help pages, and the MS experts suggested I use Alt-Space then C, which breaks the standard that Alt-F4 closes everything, like hitting the big red X.
Re: Fwd: aspell on XP
Ed Gatzke wrote: So, cmd.exe and command.exe when started from Start-Run both do not respond to Alt-F4 for me either. Other things started from cmd.exe command prompt do listen to Alt F4 c:\windows\system32\winmine.exe and dvdplay.exe both respond to Alt-F4. I run most of my stuff from a cygwin shell, but everything closes on Alt-F4 except cmd.exe and lyx.exe. Even when I start lyx from the desktop shortcut, it does not respond to Alt-F4. Even when I double click on the cmd.exe in windows/system32 it does not respond to F4. I have tried cmd.exe on about 6 xp machines, Alt-F4 does nothing on any of them for cmd.exe. I finally got around to trying this on my home PC, which runs XP Home rather than XP Pro. Under XP Home, alt-F4 did *not* kill cmd.exe. On my laptop (XP Pro), it does. I haven't had a chance to try the XP Pro machine in my office (as I'm assiduously avoiding going anywhere near the office). The exact lyx installer is the most recent, the 2.0 installer for 1.41 lyxwininstall/LyxWin141Complete-2.01.exe Even just running lyx.exe (not lyx.bat) appears to open a shell for a second before the application launches... Very odd, I wonder what is up. Maybe the shell is the root of all problems with Alt-F4. I'm not sure what goes on in that fleeting shell, but according to the task manager I use, when you run lyx.exe directly it is not running in a shell. LyX does, however, make extensive use of shell scripts (for converting graphics, running the configuration script, etc.), so it may be running some quick script at that point. This stuff is crazy. I tried posting on some MS help pages, and the MS experts suggested I use Alt-Space then C, which breaks the standard that Alt-F4 closes everything, like hitting the big red X. I agree it's strange, but as far back as I can remember, Microsoft's insistence that third-party developers adhere to their rules for Windows programs has not extended to their own programmers. Nor have they been philosophically consistent. Thus Windows 3.x came with an FTP client that had a GUI, but Windows 95/98 et seq. come only with a DOS FTP client -- even though Microsoft has been trying to phase out DOS in the last few iterations of Windows. I'm quite curious why you and Steve and I get three different behavior patterns from ostensibly the same OS. (I'm assuming that you and Steve are both using XP Pro, fully patched.) /Paul
Re: Fwd: aspell on XP
Steve Harris [EMAIL PROTECTED] writes: Paul A. Rubin wrote: Steve Harris wrote: I have LyX 1.4.2 installed and alt-f4 kills lyx but not cmd.exe My keyboard requires using an F-lock key to enable standard features. Hmm. I was going to ask John and Ed whether alt-F4 kills programs other than LyX that are being run in shells (rather than as native Windows apps) (if I'm expressing that distinction correctly). My suspicion was that maybe failure to kill cmd.exe implied inability to kill anything running in a shell. However, if alt-F4 kills LyX and not cmd.exe for So, cmd.exe and command.exe when started from Start-Run both do not respond to Alt-F4 for me either. Other things started from cmd.exe command prompt do listen to Alt F4 c:\windows\system32\winmine.exe and dvdplay.exe both respond to Alt-F4. I run most of my stuff from a cygwin shell, but everything closes on Alt-F4 except cmd.exe and lyx.exe. Even when I start lyx from the desktop shortcut, it does not respond to Alt-F4. Even when I double click on the cmd.exe in windows/system32 it does not respond to F4. I have tried cmd.exe on about 6 xp machines, Alt-F4 does nothing on any of them for cmd.exe. The exact lyx installer is the most recent, the 2.0 installer for 1.41 lyxwininstall/LyxWin141Complete-2.01.exe Even just running lyx.exe (not lyx.bat) appears to open a shell for a second before the application launches... Very odd, I wonder what is up. Maybe the shell is the root of all problems with Alt-F4. That is actually quite a good theory...because there are different versions of installers and the original port might not have had a hook(?) built into it. But it wouldn't explain a difference in behavior at an OS level, methinks. I just tried Alt-F4 on my Win98 machine Dos-prompt and that doesn't affect it. I thought perhaps your system might have had an earlier compatibility mode enabled, which would produce a different result. I'll look into it. This stuff is crazy. I tried posting on some MS help pages, and the MS experts suggested I use Alt-Space then C, which breaks the standard that Alt-F4 closes everything, like hitting the big red X.
Re: Fwd: aspell on XP
Ed Gatzke wrote: So, cmd.exe and command.exe when started from Start-Run both do not respond to Alt-F4 for me either. Other things started from cmd.exe command prompt do listen to Alt F4 c:\windows\system32\winmine.exe and dvdplay.exe both respond to Alt-F4. I run most of my stuff from a cygwin shell, but everything closes on Alt-F4 except cmd.exe and lyx.exe. Even when I start lyx from the desktop shortcut, it does not respond to Alt-F4. Even when I double click on the cmd.exe in windows/system32 it does not respond to F4. I have tried cmd.exe on about 6 xp machines, Alt-F4 does nothing on any of them for cmd.exe. I finally got around to trying this on my home PC, which runs XP Home rather than XP Pro. Under XP Home, alt-F4 did *not* kill cmd.exe. On my laptop (XP Pro), it does. I haven't had a chance to try the XP Pro machine in my office (as I'm assiduously avoiding going anywhere near the office). The exact lyx installer is the most recent, the 2.0 installer for 1.41 lyxwininstall/LyxWin141Complete-2.01.exe Even just running lyx.exe (not lyx.bat) appears to open a shell for a second before the application launches... Very odd, I wonder what is up. Maybe the shell is the root of all problems with Alt-F4. I'm not sure what goes on in that fleeting shell, but according to the task manager I use, when you run lyx.exe directly it is not running in a shell. LyX does, however, make extensive use of shell scripts (for converting graphics, running the configuration script, etc.), so it may be running some quick script at that point. This stuff is crazy. I tried posting on some MS help pages, and the MS experts suggested I use Alt-Space then C, which breaks the standard that Alt-F4 closes everything, like hitting the big red X. I agree it's strange, but as far back as I can remember, Microsoft's insistence that third-party developers adhere to their rules for Windows programs has not extended to their own programmers. Nor have they been philosophically consistent. Thus Windows 3.x came with an FTP client that had a GUI, but Windows 95/98 et seq. come only with a DOS FTP client -- even though Microsoft has been trying to phase out DOS in the last few iterations of Windows. I'm quite curious why you and Steve and I get three different behavior patterns from ostensibly the same OS. (I'm assuming that you and Steve are both using XP Pro, fully patched.) /Paul
Re: Fwd: aspell on XP
Steve Harris <[EMAIL PROTECTED]> writes: > > Paul A. Rubin wrote: > > Steve Harris wrote: > > > >> > >> I have LyX 1.4.2 installed and alt-f4 kills lyx but not cmd.exe > >> My keyboard requires using an F-lock key to enable standard features. > >> > > > > Hmm. I was going to ask John and Ed whether alt-F4 kills programs other > > than LyX that are being run in shells (rather than as native Windows > > apps) (if I'm expressing that distinction correctly). My suspicion was > > that maybe failure to kill cmd.exe implied inability to kill anything > > running in a shell. However, if alt-F4 kills LyX and not cmd.exe for So, cmd.exe and command.exe when started from Start->Run both do not respond to Alt-F4 for me either. Other things started from cmd.exe command prompt do listen to Alt F4 c:\windows\system32\winmine.exe and dvdplay.exe both respond to Alt-F4. I run most of my stuff from a cygwin shell, but everything closes on Alt-F4 except cmd.exe and lyx.exe. Even when I start lyx from the desktop shortcut, it does not respond to Alt-F4. Even when I double click on the cmd.exe in windows/system32 it does not respond to F4. I have tried cmd.exe on about 6 xp machines, Alt-F4 does nothing on any of them for cmd.exe. The exact lyx installer is the most recent, the 2.0 installer for 1.41 lyxwininstall/LyxWin141Complete-2.01.exe Even just running lyx.exe (not lyx.bat) appears to open a shell for a second before the application launches... Very odd, I wonder what is up. Maybe the shell is the root of all problems with Alt-F4. > > That is actually quite a good theory...because there are different > versions of installers and the original port might not have had a > "hook"(?) built into it. But it wouldn't explain a difference in > behavior at an OS level, methinks. I just tried Alt-F4 on my Win98 > machine Dos-prompt and that doesn't affect it. I thought perhaps > your system might have had an earlier compatibility mode enabled, > which would produce a different result. I'll look into it. > This stuff is crazy. I tried posting on some MS "help" pages, and the "MS experts" suggested I use Alt-Space then C, which breaks the standard that Alt-F4 closes everything, like hitting the big red X.
Re: Fwd: aspell on XP
Ed Gatzke wrote: So, cmd.exe and command.exe when started from Start->Run both do not respond to Alt-F4 for me either. Other things started from cmd.exe command prompt do listen to Alt F4 c:\windows\system32\winmine.exe and dvdplay.exe both respond to Alt-F4. I run most of my stuff from a cygwin shell, but everything closes on Alt-F4 except cmd.exe and lyx.exe. Even when I start lyx from the desktop shortcut, it does not respond to Alt-F4. Even when I double click on the cmd.exe in windows/system32 it does not respond to F4. I have tried cmd.exe on about 6 xp machines, Alt-F4 does nothing on any of them for cmd.exe. I finally got around to trying this on my home PC, which runs XP Home rather than XP Pro. Under XP Home, alt-F4 did *not* kill cmd.exe. On my laptop (XP Pro), it does. I haven't had a chance to try the XP Pro machine in my office (as I'm assiduously avoiding going anywhere near the office). The exact lyx installer is the most recent, the 2.0 installer for 1.41 lyxwininstall/LyxWin141Complete-2.01.exe Even just running lyx.exe (not lyx.bat) appears to open a shell for a second before the application launches... Very odd, I wonder what is up. Maybe the shell is the root of all problems with Alt-F4. I'm not sure what goes on in that fleeting shell, but according to the task manager I use, when you run lyx.exe directly it is not running in a shell. LyX does, however, make extensive use of shell scripts (for converting graphics, running the configuration script, etc.), so it may be running some quick script at that point. This stuff is crazy. I tried posting on some MS "help" pages, and the "MS experts" suggested I use Alt-Space then C, which breaks the standard that Alt-F4 closes everything, like hitting the big red X. I agree it's strange, but as far back as I can remember, Microsoft's insistence that third-party developers adhere to their rules for Windows programs has not extended to their own programmers. Nor have they been philosophically consistent. Thus Windows 3.x came with an FTP client that had a GUI, but Windows 95/98 et seq. come only with a DOS FTP client -- even though Microsoft has been trying to phase out DOS in the last few iterations of Windows. I'm quite curious why you and Steve and I get three different behavior patterns from ostensibly the same OS. (I'm assuming that you and Steve are both using XP Pro, fully patched.) /Paul
Re: Fwd: aspell on XP
Steve Harris wrote: I have LyX 1.4.2 installed and alt-f4 kills lyx but not cmd.exe My keyboard requires using an F-lock key to enable standard features. Hmm. I was going to ask John and Ed whether alt-F4 kills programs other than LyX that are being run in shells (rather than as native Windows apps) (if I'm expressing that distinction correctly). My suspicion was that maybe failure to kill cmd.exe implied inability to kill anything running in a shell. However, if alt-F4 kills LyX and not cmd.exe for you, that shoots a hole in my theory. I just tried Start-Run-Command to get the old backward-compatibility command shell. Alt-F4 won't kill that for me (I get a nag screen from Windows saying I might lose data and asking if I'm sober). I'm not sure what, if anything, that implies. Stranger and stranger ... /Paul
Re: Fwd: aspell on XP
Paul A. Rubin wrote: Steve Harris wrote: I have LyX 1.4.2 installed and alt-f4 kills lyx but not cmd.exe My keyboard requires using an F-lock key to enable standard features. Hmm. I was going to ask John and Ed whether alt-F4 kills programs other than LyX that are being run in shells (rather than as native Windows apps) (if I'm expressing that distinction correctly). My suspicion was that maybe failure to kill cmd.exe implied inability to kill anything running in a shell. However, if alt-F4 kills LyX and not cmd.exe for you, that shoots a hole in my theory. I just tried Start-Run-Command to get the old backward-compatibility command shell. Alt-F4 won't kill that for me (I get a nag screen from Windows saying I might lose data and asking if I'm sober). I'm not sure what, if anything, that implies. Stranger and stranger ... /Paul That is actually quite a good theory...because there are different versions of installers and the original port might not have had a hook(?) built into it. But it wouldn't explain a difference in behavior at an OS level, methinks. I just tried Alt-F4 on my Win98 machine Dos-prompt and that doesn't affect it. I thought perhaps your system might have had an earlier compatibility mode enabled, which would produce a different result. I'll look into it. On the Wike I noticed a post about Live-Cds. It turns out that there is a scientific constellation DVD .iso called Quantian with LyX, Imagemagick, Tetex, R, etc. But the LyX is 1.3.6 Anyway the cd-sized (700mb)clusterKnoppix boots the 2.7gig Quantian HDD iso image, which frees up the cd and is faster. knoppix floppyconfig bootfrom=/dev/hda1/quantian.iso Of course if you have a dvd player you can use it directly. The Knoppix new 5.0.1 release cd works for emergencies and can also boot a fully featured 4.3gig HDD Knoppix dvd iso. Disk partitioning can be avoided this way, the .iso is on Windows, no grub or lilo. I wanted to give this idea a bit of exposure for others, you might already know about it. This stuff is called Live because it is not intended for a hard disk install. In pursuit of the elusive Alt-F4, Stephen
Re: Fwd: aspell on XP
Steve Harris wrote: I have LyX 1.4.2 installed and alt-f4 kills lyx but not cmd.exe My keyboard requires using an F-lock key to enable standard features. Hmm. I was going to ask John and Ed whether alt-F4 kills programs other than LyX that are being run in shells (rather than as native Windows apps) (if I'm expressing that distinction correctly). My suspicion was that maybe failure to kill cmd.exe implied inability to kill anything running in a shell. However, if alt-F4 kills LyX and not cmd.exe for you, that shoots a hole in my theory. I just tried Start-Run-Command to get the old backward-compatibility command shell. Alt-F4 won't kill that for me (I get a nag screen from Windows saying I might lose data and asking if I'm sober). I'm not sure what, if anything, that implies. Stranger and stranger ... /Paul
Re: Fwd: aspell on XP
Paul A. Rubin wrote: Steve Harris wrote: I have LyX 1.4.2 installed and alt-f4 kills lyx but not cmd.exe My keyboard requires using an F-lock key to enable standard features. Hmm. I was going to ask John and Ed whether alt-F4 kills programs other than LyX that are being run in shells (rather than as native Windows apps) (if I'm expressing that distinction correctly). My suspicion was that maybe failure to kill cmd.exe implied inability to kill anything running in a shell. However, if alt-F4 kills LyX and not cmd.exe for you, that shoots a hole in my theory. I just tried Start-Run-Command to get the old backward-compatibility command shell. Alt-F4 won't kill that for me (I get a nag screen from Windows saying I might lose data and asking if I'm sober). I'm not sure what, if anything, that implies. Stranger and stranger ... /Paul That is actually quite a good theory...because there are different versions of installers and the original port might not have had a hook(?) built into it. But it wouldn't explain a difference in behavior at an OS level, methinks. I just tried Alt-F4 on my Win98 machine Dos-prompt and that doesn't affect it. I thought perhaps your system might have had an earlier compatibility mode enabled, which would produce a different result. I'll look into it. On the Wike I noticed a post about Live-Cds. It turns out that there is a scientific constellation DVD .iso called Quantian with LyX, Imagemagick, Tetex, R, etc. But the LyX is 1.3.6 Anyway the cd-sized (700mb)clusterKnoppix boots the 2.7gig Quantian HDD iso image, which frees up the cd and is faster. knoppix floppyconfig bootfrom=/dev/hda1/quantian.iso Of course if you have a dvd player you can use it directly. The Knoppix new 5.0.1 release cd works for emergencies and can also boot a fully featured 4.3gig HDD Knoppix dvd iso. Disk partitioning can be avoided this way, the .iso is on Windows, no grub or lilo. I wanted to give this idea a bit of exposure for others, you might already know about it. This stuff is called Live because it is not intended for a hard disk install. In pursuit of the elusive Alt-F4, Stephen
Re: Fwd: aspell on XP
Steve Harris wrote: I have LyX 1.4.2 installed and alt-f4 kills lyx but not cmd.exe My keyboard requires using an F-lock key to enable standard features. Hmm. I was going to ask John and Ed whether alt-F4 kills programs other than LyX that are being run in shells (rather than as native Windows apps) (if I'm expressing that distinction correctly). My suspicion was that maybe failure to kill cmd.exe implied inability to kill anything running in a shell. However, if alt-F4 kills LyX and not cmd.exe for you, that shoots a hole in my theory. I just tried Start->Run->Command to get the old backward-compatibility command shell. Alt-F4 won't kill that for me (I get a nag screen from Windows saying I might lose data and asking if I'm sober). I'm not sure what, if anything, that implies. Stranger and stranger ... /Paul
Re: Fwd: aspell on XP
Paul A. Rubin wrote: Steve Harris wrote: I have LyX 1.4.2 installed and alt-f4 kills lyx but not cmd.exe My keyboard requires using an F-lock key to enable standard features. Hmm. I was going to ask John and Ed whether alt-F4 kills programs other than LyX that are being run in shells (rather than as native Windows apps) (if I'm expressing that distinction correctly). My suspicion was that maybe failure to kill cmd.exe implied inability to kill anything running in a shell. However, if alt-F4 kills LyX and not cmd.exe for you, that shoots a hole in my theory. I just tried Start->Run->Command to get the old backward-compatibility command shell. Alt-F4 won't kill that for me (I get a nag screen from Windows saying I might lose data and asking if I'm sober). I'm not sure what, if anything, that implies. Stranger and stranger ... /Paul That is actually quite a good theory...because there are different versions of installers and the original port might not have had a "hook"(?) built into it. But it wouldn't explain a difference in behavior at an OS level, methinks. I just tried Alt-F4 on my Win98 machine Dos-prompt and that doesn't affect it. I thought perhaps your system might have had an earlier compatibility mode enabled, which would produce a different result. I'll look into it. On the Wike I noticed a post about Live-Cds. It turns out that there is a scientific constellation DVD .iso called Quantian with LyX, Imagemagick, Tetex, R, etc. But the LyX is 1.3.6 Anyway the cd-sized (700mb)clusterKnoppix boots the 2.7gig Quantian HDD iso image, which frees up the cd and is faster. knoppix floppyconfig bootfrom=/dev/hda1/quantian.iso Of course if you have a dvd player you can use it directly. The Knoppix new 5.0.1 release cd works for emergencies and can also boot a fully featured 4.3gig HDD Knoppix dvd iso. Disk partitioning can be avoided this way, the .iso is on Windows, no grub or lilo. I wanted to give this idea a bit of exposure for others, you might already know about it. This stuff is called Live because it is not intended for a hard disk install. In pursuit of the elusive Alt-F4, Stephen
Re: Fwd: aspell on XP
John Ward wrote: -- Forwarded message -- From: Paul A. Rubin [EMAIL PROTECTED] Date: Jul 7, 2006 9:56 AM Subject: Re: aspell on XP To: lyx-users@lists.lyx.org Ed Gatzke wrote: Are you sure Alt-F4 kills cmd.exe? I have tried on a couple of machines and checked other groups, Alt-F4 does not kill cmd.exe for most. Well, I just opened a command window on my laptop (XP Pro), ran a command in it, hit Alt-F4 and (a) the window vanished and (b) it's not showing up on the task list. So either I killed it or I banished it to a parallel universe. :-) I haven't tried this on XP Home, though. As far as I know, I do not have ny sort of remapping or crazy application running in the background. All apps but cmd.exe and lyx.exe respond to Alt-F4. Using cua.bind, Alt-F3, F4, Alt-4 all can be mapped to kill lyx but not Alt-F4. crazy. If you have any other ideas to try out, let me know. Thanks! Well, if it works in other apps, then it presumably has not been remapped, so I'm at a loss as to what is going on. Are your machines set up to use a non-English code page? (I'm groping in the dark here.) /Paul I'm having the same issue on XP Pro. Neither Lyx 1.4.1 or cmd.exe are killed with alt-f4, while all other apps are. -John I have LyX 1.4.2 installed and alt-f4 kills lyx but not cmd.exe My keyboard requires using an F-lock key to enable standard features.
Re: Fwd: aspell on XP
John Ward wrote: -- Forwarded message -- From: Paul A. Rubin [EMAIL PROTECTED] Date: Jul 7, 2006 9:56 AM Subject: Re: aspell on XP To: lyx-users@lists.lyx.org Ed Gatzke wrote: Are you sure Alt-F4 kills cmd.exe? I have tried on a couple of machines and checked other groups, Alt-F4 does not kill cmd.exe for most. Well, I just opened a command window on my laptop (XP Pro), ran a command in it, hit Alt-F4 and (a) the window vanished and (b) it's not showing up on the task list. So either I killed it or I banished it to a parallel universe. :-) I haven't tried this on XP Home, though. As far as I know, I do not have ny sort of remapping or crazy application running in the background. All apps but cmd.exe and lyx.exe respond to Alt-F4. Using cua.bind, Alt-F3, F4, Alt-4 all can be mapped to kill lyx but not Alt-F4. crazy. If you have any other ideas to try out, let me know. Thanks! Well, if it works in other apps, then it presumably has not been remapped, so I'm at a loss as to what is going on. Are your machines set up to use a non-English code page? (I'm groping in the dark here.) /Paul I'm having the same issue on XP Pro. Neither Lyx 1.4.1 or cmd.exe are killed with alt-f4, while all other apps are. -John I have LyX 1.4.2 installed and alt-f4 kills lyx but not cmd.exe My keyboard requires using an F-lock key to enable standard features.
Re: Fwd: aspell on XP
John Ward wrote: -- Forwarded message -- From: Paul A. Rubin <[EMAIL PROTECTED]> Date: Jul 7, 2006 9:56 AM Subject: Re: aspell on XP To: lyx-users@lists.lyx.org Ed Gatzke wrote: Are you sure Alt-F4 kills cmd.exe? I have tried on a couple of machines and checked other groups, Alt-F4 does not kill cmd.exe for most. Well, I just opened a command window on my laptop (XP Pro), ran a command in it, hit Alt-F4 and (a) the window vanished and (b) it's not showing up on the task list. So either I killed it or I banished it to a parallel universe. :-) I haven't tried this on XP Home, though. As far as I know, I do not have ny sort of remapping or crazy application running in the background. All apps but cmd.exe and lyx.exe respond to Alt-F4. Using cua.bind, Alt-F3, F4, Alt-4 all can be mapped to kill lyx but not Alt-F4. crazy. If you have any other ideas to try out, let me know. Thanks! Well, if it works in other apps, then it presumably has not been remapped, so I'm at a loss as to what is going on. Are your machines set up to use a non-English code page? (I'm groping in the dark here.) /Paul I'm having the same issue on XP Pro. Neither Lyx 1.4.1 or cmd.exe are killed with alt-f4, while all other apps are. -John I have LyX 1.4.2 installed and alt-f4 kills lyx but not cmd.exe My keyboard requires using an F-lock key to enable standard features.
