Tiny Core Extensions > Extension requests

TCSH Shell

(1/2) > >>

mocallins:
Any chance we can reincorporate TCSH shell in the current distro's
I'm a huge fan of tcsh, and found the files from back in release 2.0

Got it to work, except in TinyCore64   :(

Juanito:
tcsh added to CorePure64-11.x repo

You'll need to pm Core tcsh extension maintainer @hiro and request it to be recompiled against ncursesw - see: http://tinycorelinux.net/11.x/x86_64/tcz/src/tcsh/compile_tcsh

mocallins:
A bit of a typo here, but i sorta guessed it out, lol


--- Code: ---LIBS="-lncursesw" CC="gcc -flto -fuse-linker-plugin -mtune=generic -Os -pipe" CXX="g++ -flto -fuse-linker-plugin -mtune=generic -Os -pipe -fno-exceptions -fno-rtti" ./configure -prefix=/usr/local --localstatedir=/var
--- End code ---

Compiled, installed, and is running for me.
Thanks

    [EDIT]: Added code tags.  Rich

Rich:
Hi mocallins
Please use  Code Tags  when posting commands and responses seen in a terminal. To use  Code Tags  click on the  #  icon
above the reply box and paste your text between the  Code Tags  as shown in this example:


--- Quote ---[code][   36.176529] pcm512x 1-004d: Failed to get supply 'AVDD': -517
[   36.176536] pcm512x 1-004d: Failed to get supplies: -517
[   36.191753] pcm512x 1-004d: Failed to get supply 'AVDD': -517[/code]
--- End quote ---

It will appear like this in your post:

--- Code: ---[   36.176529] pcm512x 1-004d: Failed to get supply 'AVDD': -517
[   36.176536] pcm512x 1-004d: Failed to get supplies: -517
[   36.191753] pcm512x 1-004d: Failed to get supply 'AVDD': -517
--- End code ---

Code Tags  serve as visual markers between what you are trying to say and the information you are posting. They also preserve
spacing so column aligned data displays properly.

gadget42:
i came across this previous forum post(snippet quoted below):

--- Quote from: tinypoodle on May 30, 2014, 09:33:58 PM ---...
1. Never ever use a bash header for portable shell scripts without explicit bashisms.

2. Never ever use #!/usr/local/bin/bash as header for bash scripts, but always #!/usr/bin/env bash.

--- End quote ---
which led to several search results, and this was just one:
https://stackoverflow.com/questions/10591086/shell-script-headers-bin-sh-vs-bin-csh

which referenced this written by Bruce Barnett regarding the C and TCSH shells:
https://www.grymoire.com/Unix/CshTop10.txt

and Bruce references Tom Christiansen's essay about the C shell:
http://www.faqs.org/faqs/unix-faq/shell/csh-whynot/

interesting reading when you've got the time(and/or the interest of course)

Navigation

[0] Message Index

[#] Next page