On Windows Vista with cygwin in the colsole, which now runs bash in the home dir. It is NOT an xterm, but it runs about as well. I discovered that it is a way around the quirks of Explorer, the file manager. You open the cygwin console, cd to C:/Users/Bruce/Documents e.q and mv dirs and files.
The main quirk in Explorer is that you don't really move folders as make links to thema When I wanted to make sure a fiolder is really moved, I use UNIX commands. This way I won't splatter copies of folders around where I don't want them.
I know that Microsoft has aggreed to support POSIX which is why Cygwin works at all. I don't know if Microsoft still has its UNIX compatability package, but Cygwin is free and works fine, as far is I've seen.
I found a scanner for $5 at a garage sale, an HP scanjet 4400c, which powers up, but it is not supported in Windows Vists, no software that works, but it is old enough and simple enough that it probably works in sane under Linux.
Rather than getting the date wrong, I use the date command to start the file, just redirect the command to a new file, and edit the file, now with emacs in the console. One thing I haven't figured out is how to the the menu items that appear in emacs when you run it in a terminal emulation. I know enough emacs commands to get along well, but just nowe I wanted to see if I could change the display font, make it bigger, using menu choices.
I have noticved that this console doesn't always get updates from emacs correct and leavs cruf around from line wraps. A C-L is needed to fix this. Maybe it is better to run X11, and an xterm at least or xemacs, fortunately that requires just to click an icon in Vists.
So, now I restarted emacs from the icon that opens an xterm and xemacs, and set a comfortable font. I also tried to set auto-fill and it didn't work. A problem I saw from running emacs in the console is that the exit sequence for emacs didn't work. I will do s save and exit now.
It saved the file, but stopped me from killing emacs as an active process, I guess that is OK.
I may have just turned on auto-fill-mode, but the status bar says it it Fundemental Fill, but auto-fill did just work. I went pack and did a fill paragraph on the items above in xemacs. It worked well.
There is a tab called *Process List*, which I assumed is a list of sub processes running under xemacs, which is why I couldn't save this file a bit ago and exit.
I just set some options and attemped to save them to give xemacs my preferences. We will see if they stick. I made the font bold and large so that I can read it.
Xemacs on Cygwin seemed to have some problems saving custom setting for font and font-size. It wanted to write ~/.xemacs/custom.el, but couldn't, and it couldn't find that file when I restarted it. I may have to edit a .emacs by hand. I like the big bold font, especially since the background is this grey. I'd like to change that too. The only negative is that the emboldended Terminal font is crumby, the "s" is particularly hard to read. I just noticed that custom.el is there in a buffer, again, but I already know that I can't save it. what used to be a file, .emacs, appears to be a directory, and for some reason I can't write to it, umash problems?
The problem was that ~/.xemacs didn't exist. Why xemacs didn't create it is unclear. I guess now I have to read the man pages to find out how I can do my own customizing, such as setting auto-fill mode by default, which I like for entering text. It used to be that you added lisp to .xemacs. Maybe it is now xemacs.el and that is in .xemacs. Years ago .xemacs was a file. Maybe it always had to have the extension .el. I have forgotten lots of such details in my life. In any case I do like xemacs and fortunately I have the older hardcopy manual.