10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hello, :)
I've an issue with the creation of a directory, All work without it :mad: So, below, my scripts with the debug output :
#!/bin/bash
# PATHS
HOME_BACKUP="/home/backup"
HOME_SCRIPT="/home/scripts/test/backup_server"
TARGET="/var/www"
# DATE
DATE_Ymd=$(date +%Y-%m-%d)
#... (1 Reply)
Discussion started by: Arnaudh78
1 Replies
2. Shell Programming and Scripting
Working with IP addresses is a pain...
Here's my problem: I'm putting some interface information to a file:
3.185.201.2 | Tu1102
152.162.54.130 | Gi0/2.36
3.185.226.2 | Gi0/1
3.185.0.82 | Tu1
... (12 Replies)
Discussion started by: turk22
12 Replies
3. Shell Programming and Scripting
Hi,
I have line in input file as below:
3G_CENTRAL;INDONESIA_(M)_TELKOMSEL;SPECIAL_WORLD_GRP_7_FA_2_TELKOMSEL
My expected output for line in the file must be :
"1-Radon1-cMOC_deg"|"LDIndex"|"3G_CENTRAL|INDONESIA_(M)_TELKOMSEL"|LAST|"SPECIAL_WORLD_GRP_7_FA_2_TELKOMSEL"
Can someone... (7 Replies)
Discussion started by: shis100
7 Replies
4. AIX
More issues. The "|" key doesn't work at all, either in the text terminal or in mwm (which starts fine when I do "startx").
How am I supposed to troubleshoot without a "|" key? (2 Replies)
Discussion started by: smithfarm
2 Replies
5. OS X (Apple)
hi there, could use some basic PATH advice, i think, or something
find sometimes work, but which hasn't ever seemed to. for years!
what am i doing wrong that the commands which and find rarely work?
they used to work on the workstations i used ages ago...
running 10.5.8 because i... (4 Replies)
Discussion started by: zensnob
4 Replies
6. UNIX for Dummies Questions & Answers
totally pis*ed off.
I have a data set (xxx.txt), as follows:
chr1 3821 rs127372 A/C 0.823
chr1 3822 rs127376 A/C/G 0.899
chr1 3722 rs612634 A/C 9.22
chr1 3262 rs7152 A/T 0.22
chr1 3711 rs737 A/C/G 0.2323
.......
I only want to get those lines... (6 Replies)
Discussion started by: kaixinsjtu
6 Replies
7. UNIX for Advanced & Expert Users
when i give "ps -elf" or "ps" system gets hung.
if i press "^c" come out from it...
pls help..what should i do to get it resolved.
thanks
CKanth (4 Replies)
Discussion started by: srikanthus2002
4 Replies
8. Linux
How can I configure it?
I have a swedish keyboard with swedish keyboard setting. Everything works perfectly (едц) except that button. What can be wrong?
/Richard
++
NOTE: It seems like the computer notices the input but that the button isn't assigned to anything (the keyboard-cursor stops).... (1 Reply)
Discussion started by: riwa
1 Replies
9. UNIX for Dummies Questions & Answers
253 lab2-36:~/try_direct/another> set x=1;set y=2;@z=$x+$y
@z=1+2: Command not found.
254 lab2-36:~/try_direct/another> (11 Replies)
Discussion started by: endeavour1985
11 Replies
10. Shell Programming and Scripting
I'm using the case statement in the following script and it always takes the "*" default choice while it should be "3".
I wonder why ???
dt_auj=`date +%d`
NBLOG=`ls -al /users/notes01/LOG/t*|awk '{print $7}'|grep $dt_auj|wc -l`
case $NBLOG in
1) cat ~/LOG/console-notes > $fic_tmp1 ;;
2)... (5 Replies)
Discussion started by: Nicol
5 Replies
EDITLINE(3) Library Functions Manual EDITLINE(3)
NAME
editline - command-line editing library with history
SYNOPSIS
char *
readline(prompt)
char *prompt;
void
add_history(line)
char *line;
DESCRIPTION
Editline is a library that provides an line-editing interface with text recall. It is intended to be compatible with the readline library
provided by the Free Software Foundation, but much smaller. The bulk of this manual page describes the user interface.
The readline routine returns a line of text with the trailing newline removed. The data is returned in a buffer allocated with malloc(3),
so the space should be released with free(3) when the calling program is done with it. Before accepting input from the user, the specified
prompt is displayed on the terminal.
The add_history routine makes a copy of the specified line and adds it to the internal history list.
User Interface
A program that uses this library provides a simple emacs-like editing interface to its users. A line may be edited before it is sent to
the calling program by typing either control characters or escape sequences. A control character, shown as a caret followed by a letter,
is typed by holding down the ``control'' key while the letter is typed. For example, ``^A'' is a control-A. An escape sequence is entered
by typing the ``escape'' key followed by one or more characters. The escape key is abbreviated as ``ESC''. Note that unlike control keys,
case matters in escape sequences; ``ESC F'' is not the same as ``ESC f''.
An editing command may be typed anywhere on the line, not just at the beginning. In addition, a return may also be typed anywhere on the
line, not just at the end.
Most editing commands may be given a repeat count, n, where n is a number. To enter a repeat count, type the escape key, the number, and
then the command to execute. For example, ``ESC 4 ^f'' moves forward four characters. If a command may be given a repeat count then the
text ``[n]'' is given at the end of its description.
The following control characters are accepted:
^A Move to the beginning of the line
^B Move left (backwards) [n]
^D Delete character [n]
^E Move to end of line
^F Move right (forwards) [n]
^G Ring the bell
^H Delete character before cursor (backspace key) [n]
^I Complete filename (tab key); see below
^J Done with line (return key)
^K Kill to end of line (or column [n])
^L Redisplay line
^M Done with line (alternate return key)
^N Get next line from history [n]
^P Get previous line from history [n]
^R Search backward (forward if [n]) through history for text;
prefixing the string with a caret (^) forces it to
match only at the beginning of a history line
^T Transpose characters
^V Insert next character, even if it is an edit command
^W Wipe to the mark
^X^X Exchange current location and mark
^Y Yank back last killed text
^[ Start an escape sequence (escape key)
^]c Move forward to next character ``c''
^? Delete character before cursor (delete key) [n]
The following escape sequences are provided.
ESC ^H Delete previous word (backspace key) [n]
ESC DEL Delete previous word (delete key) [n]
ESC ESC Show possible completions; see below
ESC SP Set the mark (space key); see ^X^X and ^Y above
ESC . Get the last (or [n]'th) word from previous line
ESC ? Show possible completions; see below
ESC < Move to start of history
ESC > Move to end of history
ESC b Move backward a word [n]
ESC d Delete word under cursor [n]
ESC f Move forward a word [n]
ESC l Make word lowercase [n]
ESC m Toggle if 8bit chars display as themselves or with
an ``M-'' prefix
ESC u Make word uppercase [n]
ESC y Yank back last killed text
ESC w Make area up to mark yankable
ESC nn Set repeat count to the number nn
ESC C Read from environment variable ``_C_'', where C is
an uppercase letter
The editline library has a small macro facility. If you type the escape key followed by an uppercase letter, C, then the contents of the
environment variable _C_ are read in as if you had typed them at the keyboard. For example, if the variable _L_ contains the following:
^A^Kecho '^V^[[H^V^[[2J'^M
Then typing ``ESC L'' will move to the beginning of the line, kill the entire line, enter the echo command needed to clear the terminal (if
your terminal is like a VT-100), and send the line back to the shell.
The editline library also does filename completion. Suppose the root directory has the following files in it:
bin vmunix
core vmunix.old
If you type ``rm /v'' and then the tab key. Editline will then finish off as much of the name as possible by adding ``munix''. Because
the name is not unique, it will then beep. If you type the escape key followed by either a question mark or another escape, it will dis-
play the two choices. If you then type a period and a tab, the library will finish off the filename for you:
rm /v[TAB]munix.[TAB]old
The tab key is shown by ``[TAB]'' and the automatically-entered text is shown in italics.
BUGS AND LIMITATIONS
Cannot handle lines more than 80 columns.
AUTHORS
Simmule R. Turner <uunet.uu.net!capitol!sysgo!simmy> and Rich $alz <rsalz@osf.org>. Original manual page by DaviD W. Sanderson
<dws@ssec.wisc.edu>.
EDITLINE(3)