Home / Install Octave Windows Cygwin Emacs

Install Octave Windows Cygwin Emacs

Author: admin25/11
Install Octave Windows Cygwin Emacs Average ratng: 3,5/5 2501reviews

Hello, as mentioned recently I have a Thinkpad with Windows XP running. I installed emacs 22.x on it the way I read it someplace on the internet. Programme but under C. Emacs instead. Only printing from within emacs does not work.

However, now I found out there is Cygwin. Download Softune Workbench V3 Transportation. Well, looks great so far. Now here the question: AFAIU Cygwin is 'best choice' if one is wanting to have XP working Linux.like plus having some Xnix tools too. To enjoy Cygwin, am I to deinstall emacs the way I have it now, then to install Cygwin and reinstall emacs only this time as a Cygwin package?

Install Octave Windows Cygwin Emacs

Installing and Updating Cygwin Packages Installing and Updating Cygwin for 64-bit versions of Windows. Run setup-x86_64.exe any time you want to update or install a. Please grab Octave from here: The installer should configure everything for you. GNU Octave offers now Windows binary itself. Go to ftp://ftp.gnu.org/gnu/octave/windows/.

Does this sound reasonable? I don't mind much installing/reinstalling. As long as it is the best way to have all things running greatly.:-) Thanx in advance ray Eli Zaretskii 13:01. >From: Chris McMahan >Date: Mon, 12 Nov 2007 20:09:38 -0500 >>>I wouldn't recommend that. I am running Windows XP with Cygwin, and >I'm using the XP (w32) version of Emacs and the cygwin tools without >any problems.

I wouldn't recommend doing what you do, unless the OP likes to 'tinker' with all kinds of Emacs options and optional packages, such as cygwin-mount. There are subtle incompatibilities between Cygwin and native Windows programs (file-name conventions, console and pipe I/O, text vs. Binary I/O, signal delivery, etc.), so someone who's used for things 'to just work', like they do on GNU/Linux, is well advised to limit him/herself to either only Cygwin programs or only native Windows programs. >The cygwin version of emacs is (AFAIK) an older version. One can find a pointer to the latest one by searching the archives of the Cygwin mailing list.

>To get windowing support, you must run the Cygwin xserver. True, but where's the problem with that? An X server is available as part of the Cygwin download. JunJie 20:03.

Via by Raimund Kohl-Fuechsle on 11/12/07 Hello, as mentioned recently I have a Thinkpad with Windows XP running. I installed emacs 22.x on it the way I read it someplace on the internet.

Programme but under C. Emacs instead. Only printing from within emacs does not work. However, now I found out there is Cygwin.

Well, looks great so far. Now here the question: AFAIU Cygwin is 'best choice' if one is wanting to have XP working Linux.like plus having some Xnix tools too. To enjoy Cygwin, am I to deinstall emacs the way I have it now, then to install Cygwin and reinstall emacs only this time as a Cygwin package?

Once Were Warriors Books. Does this sound reasonable? I don't mind much installing/reinstalling. As long as it is the best way to have all things running greatly.:-) Thanx in advance ray _______________________________________________ help-gnu-emacs mailing list. Eli is an expert wrt Emacs and Windows.

And Lennart's EmacsW32 () is a very nice turnkey installer. I'm not an expert on this, and I don't mean to contradict the experts, but here is another data point for your consideration, FYI/FWIW - it is what I do and have done for a long time: - I use a vanilla Emacs binary for Windows - the 22.1 release from GNU. No EmacsW32 installer - just unzip the file to a directory. - I use vanilla Cygwin (on Windows XP).

I don't use an Emacs built for Cygwin. - I load these two Lisp files from my.emacs: This is the code I put in my.emacs to do that. It says 'If on Windows and can successfully load `cygwin-mount.el[c]', then load `setup-cygwin.el[c].' (if (and (eq system-type 'windows-nt) (require 'cygwin-mount nil t)) (require 'setup-cygwin)) That's all. I don't run an X server. I don't tinker with anything.

I have several versions of Emacs that I use on the same machine, from Emacs 20.7 through 22.1, and they are all vanilla binaries - I just put them in different folders and use different shortcuts to run them. I prefer vanilla binaries to EmacsW32 (for myself), because I don't want a customized version of Emacs - I do my own customizing.

I haven't encountered any incompatibilities or problems. I don't claim there are none, but I haven't encountered any in years of use.

AFAICT, things 'just work'. Again, I'm not arguing that this is the way to go for anyone else, but it is super easy, and it works for me. Rainer Stengele 04:19. Via by Eli Zaretskii on 11/12/07 >From: Chris McMahan >Date: Mon, 12 Nov 2007 20:09:38 -0500 >>>I wouldn't recommend that.

I am running Windows XP with Cygwin, and >I'm using the XP (w32) version of Emacs and the cygwin tools without >any problems. I wouldn't recommend doing what you do, unless the OP likes to 'tinker' with all kinds of Emacs options and optional packages, such as cygwin-mount. There are subtle incompatibilities between Cygwin and native Windows programs (file-name conventions, console and pipe I/O, text vs. Binary I/O, signal delivery, etc.), so someone who's used for things 'to just work', like they do on GNU/Linux, is well advised to limit him/herself to either only Cygwin programs or only native Windows programs. >The cygwin version of emacs is (AFAIK) an older version. One can find a pointer to the latest one by searching the archives of the Cygwin mailing list.

>To get windowing support, you must run the Cygwin xserver. True, but where's the problem with that? An X server is available as part of the Cygwin download. _______________________________________________ help-gnu-emacs mailing list Eli Zaretskii 13:59. >From: 'Drew Adams' >Date: Tue, 13 Nov 2007 01:14:01 -0800 >>>I wouldn't recommend doing what you do, unless the OP likes to >>'tinker' with all kinds of Emacs options and optional packages, such >>as cygwin-mount.

There are subtle incompatibilities between Cygwin >>and native Windows programs (file-name conventions, console and pipe >>I/O, text vs. Binary I/O, signal delivery, etc.), so someone who's >>used for things 'to just work', like they do on GNU/Linux, is well >>advised to limit him/herself to either only Cygwin programs or only >>native Windows programs. >>Eli is an expert wrt Emacs and Windows. And Lennart's EmacsW32 >() is a very nice turnkey >installer. >>I'm not an expert on this, and I don't mean to contradict the experts, I now realize that my opinion was worded too categorically: I failed to qualify it by saying that the amount and probability of subtle problems of the kind I mentioned depends on what one does with Emacs. On the extreme, if all one does is edit files, then, of course, no compatibility problems will ever be seen. In general, I'd expect the amount of potential problems to go up with usage of compilers, spell-checkers, mail agents, debuggers, shell-mode, and other features where subprocesses interact with Emacs.

David Rod 00:54.