Hi,
I need to convert user-input from '(this)' to '\(this\)' before passing it to egrep. I've tried using TR, SED and NAWK to add the backslash, but the most I ever get is a backslash without a '(' or ')'.
Any ideas?
Thanks! (13 Replies)
Hi,
I have a script which looks through an input file and takes data from the file to use within the script.
Everything works fine until the script reads the item \windows\directory\structure\ from the input file into a variable.
As unix sees the backslash as an escape character, the... (5 Replies)
Hi,
I knw its a silly question, but am a newbie to 'vi' editor. I'm forced to use this, hence kindly help me with this question.
How can i paste a chunk 'copied from' a different editor(gedit) in 'vi editor'?
As i see, p & P options does work only within 'vi'. (10 Replies)
Hi All,
I am running a script , working very fine on cmd prompt. The problem is that when I open do crontab -e even after setting editor to vi by
set EDITOR=vi it does not open a vi editor , rather it do as below.....
/////////////////////////////////////////////////////
$ set... (6 Replies)
Hello all. I am going to try my hand at compiling tarballs rather than installing packages.
I have a pretty good understanding of the process and have even compiled/installed Top from source.
But that was an easy install, I want to try something more complex using the various configure... (6 Replies)
Hi,
=============
In one of my config files, I have below command
eval echo RECORDDELIMITER '\n'
The above command results in removing backslash and outputs:
RECORDDELIMITER n
=============
Any workaround to retain the backslash after eval.
Appreciated for your... (10 Replies)
If I echo "\\" I get a backslash returned
~$ echo "\\"
\
Why doesn't this work:
string=`echo "\\"`
echo $string
I get the error message:
bash: command substitution: line 1: unexpected EOF while looking for matching `"'
bash: command substitution: line 2: syntax error: unexpected end... (2 Replies)
Why does this work when grepping for a backslash?
grep '\\' .bash_history
grep "" .bash_historyWhy does this not work when grepping for a backslash?
grep "\\" .bash_historyI know this works works but just don't understand why I need 4 backslashes when using double quotes.
grep "\\\\"... (7 Replies)
Discussion started by: cokedude
7 Replies
LEARN ABOUT DEBIAN
ansi_ctrlu
term::ansi::ctrl::unix(3tcl) Terminal control term::ansi::ctrl::unix(3tcl)__________________________________________________________________________________________________________________________________________________NAME
term::ansi::ctrl::unix - Control operations and queries
SYNOPSIS
package require Tcl 8.4
package require term::ansi::ctrl::unix ?0.1.1?
::term::ansi::ctrl::unix::import ?ns? ?arg...?
::term::ansi::ctrl::unix::raw
::term::ansi::ctrl::unix::raw
::term::ansi::ctrl::unix::columns
::term::ansi::ctrl::unix::rows
_________________________________________________________________DESCRIPTION
WARNING: This package is unix-specific and depends on the availability of two unix system commands for terminal control, i.e. stty and
tput, both of which have to be found in the $PATH. If any of these two commands is missing the loading of the package will fail.
The package provides commands to switch the standard input of the current process between raw and cooked input modes, and to query the size
of terminals, i.e. the available number of columns and lines.
API
INTROSPECTION
::term::ansi::ctrl::unix::import ?ns? ?arg...?
This command imports some or all attribute commands into the namespace ns. This is by default the namespace ctrl. Note that this is
relative namespace name, placing the imported command into a child of the current namespace. By default all commands are imported,
this can howver be restricted by listing the names of the wanted commands after the namespace argument.
OPERATIONS
::term::ansi::ctrl::unix::raw
This command switches the standard input of the current process to raw input mode. This means that from then on all characters typed
by the user are immediately reported to the application instead of waiting in the OS buffer until the Enter/Return key is received.
::term::ansi::ctrl::unix::raw
This command switches the standard input of the current process to cooked input mode. This means that from then on all characters
typed by the user are kept in OS buffers for editing until the Enter/Return key is received.
::term::ansi::ctrl::unix::columns
This command queries the terminal connected to the standard input for the number of columns available for display.
::term::ansi::ctrl::unix::rows
This command queries the terminal connected to the standard input for the number of rows (aka lines) available for display.
BUGS, IDEAS, FEEDBACK
This document, and the package it describes, will undoubtedly contain bugs and other problems. Please report such in the category term of
the Tcllib SF Trackers [http://sourceforge.net/tracker/?group_id=12883]. Please also report any ideas for enhancements you may have for
either package and/or documentation.
KEYWORDS
ansi, columns, control, cooked, input mode, lines, raw, rows, terminal
CATEGORY
Terminal control
COPYRIGHT
Copyright (c) 2006-2011 Andreas Kupries <andreas_kupries@users.sourceforge.net>
term 0.1.1 term::ansi::ctrl::unix(3tcl)