10-23-2010
I don't get your concern. "@" are just valid ascii characters. Maybe have you nulls but they would be displayed as "^@" by vi.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I want to print a man page for a command in unix, this is what I did
man command > command.txt
but when I view the output file command.txt I found there are lot of _^H characters that in the man page are actually underline character, how can I replace this _^H with underline character?
... (2 Replies)
Discussion started by: Melissa
2 Replies
2. 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
3. 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
4. SuSE
Hi,
One of our applications has this string :
xxx ¿ yyyyy
We are on Linux Suse and the character set is en_US.UTF-8. Our requirement is to replace this special character ¿ with a space. When we open the file containing this string using VI editor we see the same character as <92>
xxx... (10 Replies)
Discussion started by: LinuxTest
10 Replies
5. 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
6. Shell Programming and Scripting
Can someone help me to write a script / command to read in a file, character by character, replace any unknown ASCII characters with space. then write out the file to a new filename/
Thanks! (1 Reply)
Discussion started by: raghav525
1 Replies
7. Shell Programming and Scripting
I have to append character "0" for lines between 1 and 40 in a file.
I tried the following code.
:s/^0,1,40/g
Input:
Output: (2 Replies)
Discussion started by: pinnacle
2 Replies
8. UNIX for Dummies Questions & Answers
Hi!
I've got a shell account on a FreeBSD machine. It doesn't have 'vim' installed, but only the original 'vi' text editor ("Version 1.79 (10/23/96) The CSRG, University of California, Berkeley.")
So, in PuTTY I've chosen "UTF-8 translation" to have my non-english characters appear correctly.... (2 Replies)
Discussion started by: Gew
2 Replies
9. UNIX for Dummies Questions & Answers
Hi friends,
I am trying to add a newline char ('\n') between the query and the commit statement in the following shell script.
#! /bin/sh
echo "select * from tab; commit;" > data.sql
I have tried typing in "Ctrl-V + Ctrl-J" combination which has inserted ^@ (NUL) character but the commit... (1 Reply)
Discussion started by: royalibrahim
1 Replies
10. Shell Programming and Scripting
Hi,
Anyone can help using SED searches a character string for a specified delimiter character, and returns a leading or trailing space/blank.
Text file :
"1"|"ExternalClassDEA519CF5"|"Art1"
"2"|"ExternalClass563EA516C"|"Art3"
"3"|"ExternalClass305ED16B8"|"Art9"
...
...
... (2 Replies)
Discussion started by: fspalero
2 Replies
LEARN ABOUT DEBIAN
fvwm-bug
fvwm-bug(1) Fvwm Modules fvwm-bug(1)
NAME
fvwm-bug - report a bug in fvwm
SYNOPSIS
fvwm-bug [--help] [--version] [address]
DESCRIPTION
fvwm-bug is a shell script to help the user compose and mail bug reports concerning fvwm in a standard format. fvwm-bug invokes the editor
specified by the environment variable EDITOR on a temporary copy of the bug report format outline. The user must fill in the appropriate
fields and exit the editor. fvwm-bug then mails the completed report to the local fvwm maintainer, the fvwm workers list fvwm-work-
ers@fvwm.org, or address. If the report cannot be mailed, it is saved in the file dead.fvwm-bug in the invoking user's home directory.
The bug report format outline consists of several sections. The first section provides information about the machine, operating system,
the fvwm version, and the compilation environment. The second section should be filled in with a description of the bug. The third sec-
tion should be a description of how to reproduce the bug. The optional fourth section is for a proposed fix. Fixes are encouraged.
ENVIRONMENT
fvwm-bug will utilize the following environment variables if they exist:
EDITOR Specifies the preferred editor. If EDITOR is not set, fvwm-bug defaults to emacs.
HOME Directory in which the failed bug report is saved if the mail fails.
Fvwm 09 May 2010 (2.5.30) fvwm-bug(1)