Re: [9fans] tab completion and command history in rc
| As for command history, you are expected to | find the previous command in your rc window, edit it, copy it, paste it | to the prompt, and then run it. This is obviously more efficient than | hitting the up arrow. Don't forget, you can grep the text of the window! If your prompt is distinctive, you're done.
Re: [9fans] tab completion and command history in rc
i looked at modifying rc to write commands to a history file but it didn't seem to fit very well. maybe a hook would be better as in why not have rio log what you type, or put something between your keyboard and rio?
Re: [9fans] tab completion and command history in rc
yup. byron's rc will do the same thing. i've lost my history file a few times but i still have ~10M of it. history still performs well enough not to notice. erik Axel Belinfante [EMAIL PROTECTED] writes | | paul haahr's shell es went all the way and | made the whole interactive loop a function. | | Still using es on unix (with p9p) and | loving its persistent history | (even though my history file is now 5+ Mb) | | Axel.
Re: [9fans] tab completion and command history in rc
i thought about that. it really seems like the right solution in once sense. it moves history completely out of the purview of the shell. the bonus is that you would have history for every application. the downside is that you would have history for every application. that's explicitly not what i want. the input to ed/sam -d editing sessions interleaved with mail and rc commands doesn't seem very useful to me. rio thus feels to me like the wrong level at which to implement this functionality. to summarize: a. rio doesn't know if the input is an rc command or input to, say, sam -d. b. it would be nice to improve on the old history mechanism; rio doesn't have enough information to do this. e.g. 1. syntax errors shouldn't be logged to the history 2. multiline statements should be recalled as a unit. for me (a) would be a big problem. (b) hasn't been solved in a decade, so i guess i can live with it. ;-) - erik Charles Forsyth [EMAIL PROTECTED] writes | | i looked at modifying rc to write commands to a history file but it | didn't seem to fit very well. maybe a hook would be better as in | | why not have rio log what you type, or put something between | your keyboard and rio?
Re: [9fans] VESA ISO Changes?
The vesa code will be included with the new VM changes, which should appear within a week or so. Just out of curiosity, what type of changes are you incorporating? Are they just machine specific (x86) changes or have you been working on the mi part of the VM as well?
Re: [9fans] tab completion and command history in rc
John Floren wrote: Ouch. You seem to have unconsciously hit on some of the more hot-button topics for Plan 9 users. Tab completion is partly implemented; hit Ctrl-f. However, as a quick foray onto #plan9 will tell you, nobody seems to believe in tab completion, finding multiple ls commands and copy-pasting to be faster. As for command history, you are expected to find the previous command in your rc window, edit it, copy it, paste it to the prompt, and then run it. This is obviously more efficient than hitting the up arrow. Well, if you're just going to execute the same command again, 'up' can be great. More often than not you're going to edit the command slightly, in which case just point and click/mark with the mouse to edit and about 3 mouse clicks to run it can be faster than it sounds - and in many cases faster than various keyboard gymnastics to get to the same point you're going to edit. This is my experience atleast. If you have to poke around pages of output to find the last command, this isn't that great though. So both approaches has their strengths and flaws. Merge them.
Re: [9fans] tab completion and command history in rc
So, Rian, if there's stuff you find you miss on Plan 9, it may be you have not learned a Plan 9 way to do things, or it may be that Plan 9 environment is lacking in some way. I think many of us take a guilty pleasure in ^F. I know I do. What else might we like from the unix world that we don't talk about? It would be interesting to see. A list on the wiki would not go amiss. No harm in a bit of objectivity and soul searching. In passing, it's great news that VESA and a new VM are about to happen, shows that in important places Plan 9 is still significant enough to assign valuable resources to. But, as Ron points out, Plan 9 has its own True Way (TM) that occasionally puts a huge spanner in the works. One of my gripes is the PC keyboard. I haven't a clue what contorsions the kernel goes through to provide the final product, but the end result is not what I would ask for. For example, the Scroll LockScroll Lock tap is used to switch the console on a two-way switch I'm using: that generates two Peter faces in Plan 9. Wrong? Maybe not, but it's too different to be declared exemplary. And for all that using the mouse is demonstrated to be faster, as long as mouse _and_ keyboard are both in use, I think pulling one's hands off the keyboard to re-position the cursor is a silly necessity (as demonstrated by the introduction of cursor-right and cursor-left keys). Now let me go look at hiding that fat arrow out of the way while I type with both hands. ++L
[9fans] drawterm
Maybe this is old news to everyone else but for me the highlight of dt2k is /dev/secstore which is populated (assuming you logged in via secstore) and is completely cleared if it is written. This means you can add somthing like this to your (in the drawterm clause of the cpu case) profile: cat /mnt/term/dev/secstore | read -m /mnt/factotum/ctl echo /mnt/term/dev/secstore -Steve
Re: [9fans] cdrom drive problems
Sergey Zhilkin wrote: Just try the floppy disk from plan9.bell-labs.com http://plan9.bell-labs.com :) On 11/4/05, *John Floren* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Hello everyone. I've got an old Pentium machine here, and I'm trying to install Plan 9 on it. It has a hard drive at primary master and a cdrom drive at secondary master. When I put in the boot cd (downloaded from the Bell Labs website) and try to boot, I can get as far as a boot prompt saying boot devices: fd0 boot from: After that, no dice. I've tried the old reliable sdD0!cdboot!9pcflop.gz, but I get an error saying that there is no cdboot partition on the disk. This same disk loads fine in qemu, so it is not a burn problem. Could it be that my IDE controller is simply not supported? Would using the 9grid.de http://9grid.de iso image help? Thanks John Floren -- http://nuwen.net/~digi/cluster Jealousy is all the fun you think they have. Problem is locating a floppy disk :-) -- http://nuwen.net/~digi/cluster Every journalist has a novel in him, which is an excellent place for it.
Re: [9fans] drawterm
Hi I just downloaded the windows version and seems that this new version can't be used with the same params of the old one. I try to run it without params and with the common /? -h --help, and i only get a crash. I think it try to open some environment variables that are missing. (i can send you the complete dump from windows if needed) How can be used this new version? are there some env vars I must use? Thanks Gabi 2005/11/4, Russ Cox [EMAIL PROTECTED]: I am almost ready to declare dt2k stable.The random lock-ups were due to suspect X11 usethat I cleaned up a few weeks ago.The fcp bug I mentioned before turns out to be aproblem with Plan 9, not with drawterm.The bug was in devssl (or in devmnt, depending on how you look at it),not in drawterm.There is a new /sys/src/9/port/devssl.cand devmnt.c on sources.There are new drawterm binaries at http://swtch.com/drawterm/If you build yourself a kernel with the new devssl/devmntand are running the latest drawterm and see it crash ordo something else wrong, please let me know.The latest drawterm has one new feature: if you are running a plan9port factotum, then drawterm will use it.Russ
Re: [9fans] drawterm
There are new drawterm binaries at http://swtch.com/drawterm/ I almost don't dare to ask... anybody tried to compile it (with success) for sunos 5.8? To answer my own question: after a little struggle I have a drawterm. When I start it with my usual -a and -c flags it says: | cpu: cannot write user/domain choice in p9any: | '/mnt/factotum/ctl' does not exist | | goodbye Is this something I missed in the struggle? Or the effect of a too old p9p installation? Or? (running cpu from a plan9 terminal works fine, as does old drawterm) Axel.
Re: [9fans] drawterm
In your message to me you wrote: In message [EMAIL PROTECTED]you write: There are new drawterm binaries at http://swtch.com/drawterm/ I almost don't dare to ask... anybody tried to compile it (with success) for sunos 5.8? To answer my own question: after a little struggle I have a drawterm. When I start it with my usual -a and -c flags it says: | cpu: cannot write user/domain choice in p9any: | '/mnt/factotum/ctl' does not exist | | goodbye Is this something I missed in the struggle? Or the effect of a too old p9p installation? Or? (running cpu from a plan9 terminal works fine, as does old drawterm) commenting out the 'exits' at the end of 'fatal' and adding some debug prints shows me a bit more. seems like the '/mnt/factotum/ctl does not exist somehow is stuck from a previous error and not reset. reading p9any negotiation: [EMAIL PROTECTED] cpu: cannot write user/domain choice in p9any: 11 != 20: p9sk1 cs.utwente.nl cpu: cannot write p9sk1 challenge: (factotum ctl err msg) [EMAIL PROTECTED] password: cpu: cannot send ticket and authenticator back in p9sk1: cs gave empty translation list cpu: can't authenticate slurp: cs gave empty translation list cpu: wrting network: dir: fd out of range or not open cpu: wanting for FS: fd out of range or not open: fd out of range or not open remote cpu: goodbye Axel.
Re: [9fans] drawterm
i just downloaded it. ran it under fc4 and it drops core. now, if i can just find out where they put the core file!! bc ---BeginMessage--- There are new drawterm binaries at http://swtch.com/drawterm/ I almost don't dare to ask... anybody tried to compile it (with success) for sunos 5.8? To answer my own question: after a little struggle I have a drawterm. When I start it with my usual -a and -c flags it says: | cpu: cannot write user/domain choice in p9any: | '/mnt/factotum/ctl' does not exist | | goodbye Is this something I missed in the struggle? Or the effect of a too old p9p installation? Or? (running cpu from a plan9 terminal works fine, as does old drawterm) Axel.---End Message---
