hobie@sq.uucp (Hobie Orris) (12/21/87)
Will it happen? Is anyone working on this? If so, I have a suggestion
which I think will be of general usefulness. Up in the top of my CLI window it
says "AmigaDOS" in the title bar. I don't need to be reminded that I'm using
an Amiga. I think it would be much more useful to have the name of my current
directory there, like "DH0:/src/widget" so I don't have to type in "pwd" to findout where I am. Perhaps a definable title bar that you could specify what you
want on the title bar, like "$pwd\t\t$date\t\t$lasterr" and have it update auto-
magically whenever these values change, or something. I'd do this thing myself
but I don't have MY.LIB, which I believe is necessary to compile the shell.
Hobie Orris |
guest of SoftQuad Inc., Toronto, Ont. |"There'll be no more giant leeches
{ihnp4 | decvax | ? }!utzoo!sq!hobie | When you find the good Lord Jesus"mp1u+@andrew.cmu.edu (Michael Portuesi) (12/22/87)
hobie@sq.uucp (Hobie Orris) writes: > Up in the top of my CLI window it says "AmigaDOS" in the title bar. > I don't need to be reminded that I'm using an Amiga. I think it > would be much more useful to have the name of my current > directory there, like "DH0:/src/widget" so I don't have to type in > "pwd" to findout where I am. A "CD" program to do exactly that just popped up on comp.binaries.amiga...you could certainly use that with the existing shell. Though this new CD sounds really cool (finally, a use for the titlebar on a CLI window), I am loathe to use it since on my one-drive system I make a large number of commands RESIDENT, and thus am restricted to the AmigaDOS BCPL commands (no flames about RESIDENT, please...I use it responsibly, have *never* had any problems with it, and it makes life with one disk drive SO much easier). Maybe when the fairy godmother brings me a hard disk, and I actually have a place to put the system software... One thing the shell writers (or maybe the author of ConMan) might want to consider...on the Andrew environment here at CMU, you talk to csh in a "Typescript" window. This window not only saves a transcript of your session (you can scroll back over previous junk from your session with a scrollbar), it also allows you to mouse off a section of text, select "Execute" from a pop-up menu, and have it execute the selected region of text. If you already typed other text at the prompt before you moused off the text, Typescript appends the moused-off text to the end of the string you typed and executes the whole thing. In addition, you can add your own menu selections to the Typescript pop-up menus. When you select that option, it types the string associated with that menu option to csh. Thus you can place your oft-used commands in menus. Adding options along these lines to a shell or ConMan-type console driver might make for bloated software, but it is really nifty to use. --M Michael Portuesi / Carnegie Mellon University ARPA/UUCP: mp1u+@andrew.cmu.edu BITNET: rainwalker@drycas "little things remind me of you...cheap cologne and that damn song too!" --The Flirts, "Jukebox"
richard@gryphon.CTS.COM (Richard Sexton) (12/22/87)
In article <1987Dec20.175713.7918@sq.uucp> hobie@sq.UUCP (Hobie Orris) writes: > > > Will it happen? Is anyone working on this? If so, I have a suggestion Me too. Have seperate input and output areas of the screen like Apollos DM. Comments ? -- "Well, they say that Santa Fe is less than 90 miles away" richard@gryphon.CTS.COM || {ihnp4!crash, hplabs!hp-sdd!crash}!gryphon!richard
dml@loral.UUCP (Dave Lewis) (12/25/87)
In article <1987Dec20.175713.7918@sq.uucp> hobie@sq.UUCP (Hobie Orris) writes: >says "AmigaDOS" in the title bar...name of my current directory there, like >"DH0:/src/widget" so I don't have to type in "pwd" to findout where I am. >Perhaps a definable title bar that you could specify what you want on the >title bar, like "$pwd\t\t$date\t\t$lasterr" and have it update auto- >magically whenever these values change, or something. I'd do this thing myself >but I don't have MY.LIB, which I believe is necessary to compile the shell. I compiled Dillon/Drew version 2.07m without any custom libraries; I'm using it now. Great idea, putting useful info in the title bar...it should be imple- mented like _prompt, user-definable. New special variable _titlebar. I've wanted something in Shell ever since I started using 2.05: More!! I HATE typing \ - <backspace> frantically as my text runs off the top of the screen, and I don't like going to the disk for such a common command. Even if it's just a page break (no fancy options, like "b", "s", ":n" etc. to reduce the size) it would be better than nothing. Bob Leivian's "Less" would be great except for two problems: it's over 22K bytes, and it doesn't handle the Amiga screen control codes -- it barfs "^[[m3text^[[m0" all over the screen. Another thing - "dir" needs some fixing. Most of the time I just want to see filenames. I don't need to know all the info, and I don't want to jump on a key to stop it from scrolling off the screen. Make the default "dir -s", save "dir -l" for when I really want it. (I've done `alias l "dir -s"' and `alias ll dir') And reformat the "-l" display -- I'm tired of seeing this: A file rwed 22364 46 07-Aug-87 17:20:13 'Nother file rwed 4480 9 04-Sep-87 22:43:08 Great big humungous file name rwed 27243 55 08-Oct-87 14:02:55 Not so humungous file name rwed 8820 17 22-Nov-87 05:42:30 Unix has the right idea: rwed 22364 46 07-Aug-87 17:20:13 A file rwed 4480 9 04-Sep-87 22:43:08 'Nother file rwed 27243 55 08-Oct-87 14:02:55 Great big humungous file name rwed 8820 17 22-Nov-87 05:42:30 Not so humungous file name Finally, change the "devinfo" command. "info" should provide a display exactly like the Arp "info" (if disk is not in drive, just say so without making an error). "info df0:" would display only the one drive. I'll do it myself eventually, but I'd hate to have to hack my changes into every new version of Shell.... Now that I'm done bitching...Shell's really great. I especially like the "if -f" option added to 2.07m, which allows me to reboot fast when running Aztec C. I keep Z (renamed to Vi), the entire Include directory, c.lib and m.lib in VD0:, using ".login" to copy them at power-up. Used to be I had to do "If exists VD0:Include" in Startup-sequence, then choose between "Shell .login" to copy everything or "Shell .relogin" to skip copying. Now I can check for several directories individually in .login and copy if they're not present. VD0: is running in $C00000 RAM and sometimes AmigaDOS crumbles the magic cookies on reboot when VD0: is near full. 'Nother thing -- somebody said a while ago that if you copy all the commands and other files referenced by Startup-sequence to the disk FIRST, the Amiga will boot up faster. "It's twue, it's twue!" Sometimes twice as fast. So, in the S: directory of every bootable disk, I have a "Make<diskname>.sh" file containing commands to create a system disk from scratch. Format, Install, and lots of copy, copy, copy in the correct order. ------------------------------- Dave Lewis Loral Instrumentation San Diego hp-sdd --\ ihnp4 --\ sdcrdcf --\ bang --\ kontron -\ csndvax ---\ calmasd -->-->!crash --\ celerity --->------->!sdcsvax!sdcc3 --->--->!loral!dml (uucp) dcdwest ---/ gould9 --/ Working with a single-tasking computer is like cooking on a stove with only one burner. Multi-finders and their ilk allow you to put different pans on the burner. -------------------------------
john13@garfield.UUCP (John Russell) (12/26/87)
In article <1507@loral.UUCP> dml@loral.UUCP (Dave Lewis) writes: > 'Nother thing -- somebody said a while ago that if you copy all the commands >and other files referenced by Startup-sequence to the disk FIRST, the Amiga >will boot up faster. "It's twue, it's twue!" Sometimes twice as fast. So, in And for people without any Megs, putting the libraries on a disk first gives you a major speedup when linking. This will also work for large programs you load often, eg if "cc" grinds your disk when loading, it will whisper if it's one of the first things on the disk. John -- To preserve deniability, I have not informed the University of this posting. But if I had, they would have been 100% behind it, yessirree bob. This posting has statements that are evasive, misleading, and just plain wrong. But that is only because I love the UseNet with all my heart!
joseph@garfield.UUCP (Joseph Dawson) (12/27/87)
Ideas:
I would like the option to NOT have sorted DIR! I would like to have
the option of using the DIR command like in 2.5. The best way of having
it would be with a flag of some sort like "DIR -N". Then I could alias
that to DIR.
Now for some questions:
Why can't shell have a RUN command? (Not load the AmigaDOS run!)
Why can't we RUN shell commands? (I would love to RUN SOURCE FILENAME!)
One last thing...
To the makers of SHELL, VT100 and DME! "****THANK-YOU****"
Joseph Dawsoncthulhu@athena.mit.edu (Jim Reich) (01/05/88)
>One thing the shell writers (or maybe the author of ConMan) might want to >consider...on the Andrew environment here at CMU, you talk to csh in a >"Typescript" window. This window not only saves a transcript of your session >(you can scroll back over previous junk from your session with a scrollbar), There is a shareware program out there called "rollback" which does just that. It is even compatible with ConMan. Takes some memory, but it can be useful. Unfortunately, it interacts with some background program on my system disk which I've never bothered to track down, but it's worth a try. >it also allows you to mouse off a section of text, select "Execute" from a >pop-up menu, and have it execute the selected region of text. If you already >typed other text at the prompt before you moused off the text, Typescript >appends the moused-off text to the end of the string you typed and executes the whole thing. In addition, you can add your own menu selections to the >Typescript pop-up menus. When you select that option, it types the string >associated with that menu option to csh. Thus you can place your oft-used >commands in menus. This would definitely be worthwhile. Anyone out there have some free time? >Adding options along these lines to a shell or ConMan-type console driver >might make for bloated software, but it is really nifty to use. ... and the mouse text selection wouldn't be THAT bloating for CON:. Better yet, it could be implemented through (gasp) the CLIPBOARD DEVICE! Why does almost nobody support the poor clipboard? That's one thing I REALLY miss from my Mac days, and with IFF, it shouldn't be THAT BAD... Picture pasting into the CLI, or from the CLI into a terminal program, or whatever! -- Jim
john13@garfield.UUCP (John Russell) (01/06/88)
In article <2135@bloom-beacon.MIT.EDU> cthulhu@athena.mit.edu (Jim Reich) writes: >... and the mouse text selection wouldn't be THAT bloating for CON:. Better >yet, it could be implemented through (gasp) the CLIPBOARD DEVICE! Why does >almost nobody support the poor clipboard? That's one thing I REALLY miss >from my Mac days, and with IFF, it shouldn't be THAT BAD... Picture >pasting into the CLI, or from the CLI into a terminal program, or whatever! Uh oh, looks like it's time for more examples :-) ! The only program source I've ever seen that did anything with the clipboard was from Andy Finkel on an early Fish disk, and though I don't remember it exactly I do remember thinking that someone would need a very high level of IFF awareness and perhaps a detailed understanding of how the clipboard worked in order to put the code to any good use. The way to get people to use the more complex features of the OS, perhaps to take the 'long way round' in order to be fully compatible with things like IFF, system IO (cf. the recent discussions here about that), etc is to make sure that detailed info (even the very very basic stuff) is readily available in the form of working programs that perform many of the same functions they would like to implement. If this calls for periodic rehashing of the same topics, so be it; it's a lot easier to re-post a program from 2 years back that few people know about than to write it from scratch. How about the SnipIt program mentioned by Peter da Silva a while back? Is there source for that, and is it being posted? John -- "I hate to be the one to tell you this, Bryce, but there's more to life than interactive systems analysis." "I know. It also involves number crunching!" -- Max Headroom