Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: Not able to input \ backslash when vi editor
Top Forums UNIX for Beginners Questions & Answers Not able to input \ backslash when vi editor Post 303026757 by Neo on Monday 3rd of December 2018 03:39:56 AM
Old 12-03-2018
That really depends on your terminal settings and having your keyboard set up normally or correctly:

On MacOX

Code:
$ vi test.text

(type \\\\\\\ in terminal)

Code:
$ cat test.text

\\\\\\ 

$

Works fine for me on MacOS... now try Linux:

Code:
$ vi text.text

(type \\\\\\\ in terminal)

Code:
$ cat text.text
\\\\\\\
$

Sounds like your keyboard may not be mapped properly, that is the first thing that come to mind.
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Adding a backslash to users' input

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

backslash issues

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

Pasting text in VI editor from a different editor

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

set EDITOR=vi -> default editor not setting for cron tab

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

Escaping backslash

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 :Licen

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

./configure backslash questions

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

eval removes backslash

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

Echo backslash

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

grep for a backslash question

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 SUSE

ansi_ctrlu

term::ansi::ctrl::unix(n)					 Terminal control					 term::ansi::ctrl::unix(n)

__________________________________________________________________________________________________________________________________________________

NAME

       term::ansi::ctrl::unix - Control operations and queries

SYNOPSIS

       package require Tcl  8.4

       package require term::ansi::ctrl::unix  ?0.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

COPYRIGHT

       Copyright (c) 2006 Andreas Kupries <andreas_kupries@users.sourceforge.net>

term									0.1						 term::ansi::ctrl::unix(n)
All times are GMT -4. The time now is 10:41 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy