Does anyone know of a way to mimic the up arrow/down arrow type bash behavior within a shell script?
Say I have a scripted menu, and would like to be able to up arrow to bring up the last X number of lines of user input?
Thanks to anybody with a suggestion. :) (0 Replies)
Hello all, I have a bash function that opens Safari (I'm on OS X) with a specified argument.
Here it is :
function safari
{
#Safari bash function
TLDS=( "http://www." ".com" ".org" ".net" ".gov" ".edu" )
if ; then
open -a Safari ${TLDS}$2${TLDS}
elif ; then
open -a Safari... (0 Replies)
hii to all
i am developing a simple unix shell in c i want to add history feature in that how could i do that plz help if there is any tutorial or website plz put it here
history feature should be like that in bash, when press up key show the previous command typed in console
plz be... (1 Reply)
By default, we use ksh (88) as our shell. I prefer bash, so I added this line to my .profile:
exec bash -o viI also added this to my .bashrc?:
#***********************************************
#These are important tweaks specific to BASH:
#***********************************************... (1 Reply)
Hello
How to configure, or where to have each session history in different file
Example: someone is connecting as root and at this time is creating file in which we have history of executed command
to server is connecting another user and is created another file with command executed by... (1 Reply)
Is it possible to use the keyboard UP ARROW in place of k to recall history? If so, how/what do I need to do change terminal emulation, etc.?
TIA,
George (7 Replies)
Moderators,
Please excuse if I am in the wrong section.
I have a question that someone may know the answer to. We know that a current bash shell keeps a record of all commands in a buffer. When the shell is terminated this buffer is written out to ~/.bash_history for the user.
I know... (2 Replies)
Hi,
I want to export bash history to a file, I used the following command
history > /home/administrator/bashHistory
But the exported file only contains commands with line number from 996 to the last one, How to export all the commands including commands before line 996?
Thanks a lot.... (2 Replies)
Hi
I am trying to increase the number of commands recorded in my .bash_history file.
I followed what is indicated and have add to my .bashrc
export HISTCONTROL=ignoreboth
export HISTSIZE=1000000
export HISTFILESIZE=1000000
export HISTIGNORE='ls'but the .bash_history only contains 690... (5 Replies)
# check host value regex='^(||1|2|25)(\.(||1|2|25)){3}$' if ')" != "" ]; then if ]; then echo host $host not found exit 4 fi elif ]; then echo $host is an invalid host address exit 5 fi
espeacailly the top regex part?
---------- Post updated at 06:58 PM ---------- Previous update was... (1 Reply)
Discussion started by: kevin298
1 Replies
LEARN ABOUT POSIX
libbash
LIBBASH(7) libbash Manual LIBBASH(7)NAME
libbash -- A bash shared libraries package.
DESCRIPTION
libbash is a package that enables bash dynamic-like shared libraries. Actually its a tool for managing bash scripts whose functions you may
want to load and use in scripts of your own.
It contains a 'dynamic loader' for the shared libraries ( ldbash(1)), a configuration tool (ldbashconfig(8)), and some libraries.
Using ldbash(1) you are able to load loadable bash libraries, such as getopts(1) and hashstash(1). A bash shared library that can be loaded
using
ldbash(1) must answer 4 requirments:
1. It must be installed in $LIBBASH_PREFIX/lib/bash (default is /usr/lib/bash).
2. It must contain a line that begins with '#EXPORT='. That line will contain (after the '=') a list of functions that the library
exports. I.e. all the function that will be usable after loading that library will be listed in that line.
3. It must contain a line that begins with '#REQUIRE='. That line will contain (after the '=') a list of bash libraries that are
required for our library. I.e. every bash library that is in use in our bash library must be listed there.
4. The library must be listed (For more information, see ldbashconfig(8)).
Basic guidelines for writing library of your own:
1. Be aware, that your library will be actually sourced. So, basically, it should contain (i.e define) only functions.
2. Try to declare all variables intended for internal use as local.
3. Global variables and functions that are intended for internal use (i.e are not defined in '#EXPORT=') should begin with:
__<library_name>_
For example, internal function myfoosort of hashstash library should be named as
__hashstash_myfoosort
This helps to avoid conflicts in global name space when using libraries that come from different vendors.
4. See html manual for full version of this guide.
AUTHORS
Hai Zaar <haizaar@haizaar.com>
Gil Ran <ril@ran4.net>
SEE ALSO ldbash(1), ldbashconfig(8), getopts(1), hashstash(1)colors(1)messages(1)urlcoding(1)locks(1)Linux Epoch Linux