12-03-2018
Maybe this will help you:
REF:
6.15 Non-US Keyboard Mappings Not Reliable in Virtual Machine Console
Quote:
6.15 Non-US Keyboard Mappings Not Reliable in Virtual Machine Console
Non-US keyboard mappings do not behave predictably in the virtual machine console available in the Oracle VM Manager Web Interface. To ensure the best possible behavior within the Virtual Machine console, it is advisable to set all keyboard mapping options en-us on your virtual machines and to use a US keyboard when working with the virtual machine console. This is not a requirement, but currently not all keyboard mappings behave as expected within the virtual machine console.
Bug 18089107
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
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)
Discussion started by: netguy
13 Replies
2. UNIX for Dummies Questions & Answers
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)
Discussion started by: Bab00shka
5 Replies
3. UNIX for Dummies Questions & Answers
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)
Discussion started by: harishmitty
10 Replies
4. Shell Programming and Scripting
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)
Discussion started by: aarora_98
6 Replies
5. UNIX for Dummies Questions & Answers
I have a variable containt something like this, c:\mask\mask. How can I escape "\" in the values? I want the value as it it. (9 Replies)
Discussion started by: swmk
9 Replies
6. Solaris
Epic Editor was not able to obtain a license for your use. Feature Epic Editor :License server is down (1 Reply)
Discussion started by: durgaprasadr13
1 Replies
7. UNIX for Dummies Questions & Answers
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)
Discussion started by: RobertSubnet
6 Replies
8. UNIX for Dummies Questions & Answers
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)
Discussion started by: axes
10 Replies
9. Shell Programming and Scripting
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)
Discussion started by: locoroco
2 Replies
10. UNIX for Advanced & Expert Users
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
ex(1) General Commands Manual ex(1)
Name
ex, edit - text editor
Syntax
ex [ - ] [ -v ] [ -x ] [ -t tag ] [ -r ] [ +command ] [ -l ] name...
edit [ ex options ]
Description
The editor is the root of a family of editors: and The editor is a superset of with the most notable extension being a display-editing
facility. Display-based editing is the focus of
The name argument indicates the files to be edited.
Options
- Suppresses all interactive-user feedback. This option is useful in processing editor scripts in command files.
-v Equivalent to using rather than
-t Equivalent to an initial tag command, that is, editing the file containing the tag and positioning the editor at its definition.
-r Used to recover after an editor or system crash. It recovers by retrieving the last saved version of the named file. If no file is
specified, it displays a list of saved files.
-R Sets the read-only option at the start.
+command
Indicates that the editor should begin by executing the specified command. If the command is omitted, it defaults to $, positioning
the editor at the last line of the first file, initially. Other useful commands here are scanning patterns of the form +/pattern or
line numbers.
-l Sets up for LISP. That is, it sets the showmatch and lisp options. The -x option is available only if the Encryption layered product
is installed.
-x Causes to prompt for a key. The key is used to encrypt and decrypt the contents of the file. If the file contents have been encrypted
with one key, you must use the same key to decrypt them.
Restrictions
The command causes all marks to be lost on lines changed and then restored if the marked lines were changed.
The command does not clear the buffer modified condition.
The z command prints a number of logical rather than physical lines. More than a screenful of output may result if long lines are present.
File input/output errors do not print a name if the command line minus sign (-) option is used.
There is no easy way to do a single scan ignoring case.
The editor does not warn you if you place text in named buffers and do not use it before exiting the editor.
Null characters are discarded from input files, and cannot appear in output files.
Files
/usr/lib/ex?.?recover recover command
/usr/lib/ex?.?preserve preserve command
/etc/termcap terminal capabilities
~/.exrc editor startup file
/tmp/Exnnnnn editor temporary
/tmp/Rxnnnnn named buffer temporary
/usr/preserve preservation directory
See Also
awk(1), ed(1), grep(1), sed(1), vi(1), termcap(5), environ(7)
"Edit: A Tutorial" and the "Ex Reference Manual" in the
Supplementary Documents, Volume 1: General User
ex(1)