I tend to have a low attention span, so when I get a proof-of-concept like this up and running (and prove it works), even if the final results are not "polished", I then want to "call it good enough" and quickly move on to the next project.
This is me too except for the attention span. As soon as I find a solution to something I let others better it.
And as for doing something different I have done some bizarre stuff on here... <wink> /Me awaits the mickey take... ;oD
OT: Here is a small snippet for a terminal window you might like under OSX 10.14.6 on this MBP, solved and going into the Campimeter code.
Enjoy...
Last edited by wisecracker; 01-30-2020 at 03:29 AM..
Reason: Corrected the "shebang", 30-01-2020. Thanks Ravinder...
These 2 Users Gave Thanks to wisecracker For This Post:
I am interested in knowing if anyone out there has been using the BSD UNIX that underlies
MacOS X. Is this an "industrial strength" version of UNIX? Can I run X-Windows on such
a machine? How about TeXing, pythoning, PERLing or using other useful UNIX goodies
near and dear to my shrunken... (1 Reply)
1) How can I stop Vuze from reporting the following error: "Too many open files" ?
2) What directory do I need to be in to effectively utilize this command:
sudo bash -c 'ulimit -n 8192; sudo -u username ./azureus' ?
3) Is this the maximum number of files that I can allot to Vuze on OS X... (1 Reply)
Dear all,
I use awk quite a bit for data wrangling ... today I find weird behavior that I cannot wrap my head around.
if I execute the following command (simplified to illustrate the behavior ... nothing to do with the real command)
bash-3.2$ awk... (3 Replies)
why,just beacuse that its the bottom layer uses a small amount of bsd code? In my opinion, macos and Unix are completely different. The directories are long directory structures. For example, /application, /system, /user, /volumes, etc. are completely different from the traditional /bin/ /sbin... (5 Replies)
Interestingly Apple has decided to switch the default shell for new users from bash to zsh in MacOS Catalina (10.15)
Use zsh as the default shell on your Mac - Apple Support
Another interesting fact is that Catalina also comes with /bin/dash (5 Replies)
Hi all...
This was the original code I created to expand a terminal on the fly using Python 2.6.x to the now 3.8.0 without modification under OSX 10.7.5.
I had no idea at the time that the MBP terminal could be full screen until here:... (0 Replies)
Discussion started by: wisecracker
0 Replies
LEARN ABOUT DEBIAN
win
win(1) General Commands Manual win(1)NAME
win - Terminal emulator
SYNOPSIS
win [-v] [-t name] [command [argument ...]] address
OPTIONS -v If the -v option is present, win prints its version number and date and exits.
-tname If the -t option is present, win uses +name as the final part of the tag name of its window.
DESCRIPTION
win must be able to connect to a running wily(1). win attaches to a window. If the -t option is present, the final part of the tag name
is name. If command is present, the final part of the tag name is +command. Otherwise, the final part of the tag name is +win. The first
part of the tag name is the current working directory.
win runs a program in a child process. The child process is the leader of a process group and is connected to win by a pseudo-terminal.
If command is specified, the child process runs
$SHELL -c 'command argument ...'
otherwise it runs
$SHELL -i
If SHELL is not found in the environment, /bin/sh is used.
TERM=win is placed in the environment of the running program.
Output from the running command appears in the window. The point after the last output from the running command is known as the output
point. Further output from the running command appears just before the output point. The output point is initially at the end of the win-
dow.
Normal wily editing commands work in the window. When a newline, interrupt character, or end-of-file character is created after the output
point, the text between the output point and the last newline, interrupt character, or end-of-file character in the window (inclusive) is
passed to the running program as input.
The interrupt character is control-C and the end-of-file character is control-D. The pseudo-terminal initially is configured so that these
are recognized with their normal meanings.
The B2 commands beginning with the |, <, or > characters or an upper case letter are executed normally by wily. Other B2 are first termi-
nated with a newline, if they are not already, and are then appended to the buffer (and thereafter passed to the running program).
RETURNS
win returns zero if it is able to successfully create the child process, otherwise it returns non-zero.
EXAMPLES
Run a terminal emulator within wily
win
Run FTP within wily
win ftp
Run rlogin within wily
win -t host.domain rlogin -8 host.domain
SEE ALSO wily(1)Tag(1)Man(1)BUGS
win doesn't follow changes to the terminal attributes. In particular, there is no way to stop echoing or to change its concept of the
interrupt and eof characters.
rlogin seems to need -8 and, annoyingly, sets echo and onlcr. The latter can be fixed in your .rcrc:
if ( ~ $TERM win ) {
stty -echo -onlcr
}
win doesn't follow changes to the terminal attributes. In particular, there is no way to stop echoing or to change its concept of the
interrupt and eof characters.
WEdestroy messages aren't yet passed by wily. Thus, Del and Delcol can delete the window yet leave win running.
There is a race condition; the user can press newline and then delete text before win has a chance to read it.
AUTHOR
win was originally written by Gary Capell (gary@cs.su.oz.au). Alan Watson (alan@oldp.nmsu.edu) rewrote it and added support for arguments,
pseudo-terminals instead of pipes, and execution of certain B2 commands by wily. The pseudo-terminal support in 9term, written by Matty
Farrow (matty@cs.su.oz.au), was a great help.
1R1.1L1 of 1D1 win(1)