in vim editor, if i want to save that file, i have to save and exit (ZZ). i want to be able to save the file without exiting. that way, i can compile the code and if i need to change some coding, i can just switch over without retyping "vim myprogram.c". is there a way to save without exit?... (7 Replies)
Here is my problem,
I manage a SunOs 5.8 Server, vi is the default command line
editor, I have a line on each users .kshrc profile as follows:
export EDITOR=/bin/vi
I want to use vim as the command line editor, the below line
doesn't work
export EDITOR=/bin/vim
Thank you (1 Reply)
Hi,
I want to use ctags for multiple folders containing .c and .h files. Can anyone help me with it? I have been using ctags for 1 folder at a time but I would like to link multiple folders and access all .c files at a time using ctags.
Thanks,
shahsm (1 Reply)
Hi,
i am using VIM editor through Putty. By the option of Syntax on in .vimrc file i am able to see syntax colors in .c and .cpp files but not in the files with .pc extension.
How can this be done?
:confused: (2 Replies)
I ran into this issue and thanks to various postings in various forums, was
able to figure out the solution but didn't see one posting that laid the
whole issue out cleanly. So thought the following might help others ...
------------------------------------------------------------------------... (2 Replies)
Hi,
I entered the following text in a new file through vim: "Four score and seven years ago" saved and exit.
When I looked at the file size, it was 31B, although is supposed to be 30. I reedited the file (again with vim) to check for errors, but everything seemed fine. When I opened the file... (3 Replies)
how to turn on the color in vim editor."syntax on" is not working for me.
when i do syntax on it only make some of the text basically header files nd functions name in bold.i am working on "secure crt" ..my vim is in /usr/share
i also have .vimrc file in my home folder "~"
Please help me... (11 Replies)
I downloaded vim.7.2 and compiled the vim source .
Added the vim binary path to PATH (Because iam not the root of the box)
when i load the file using vim it throws me an error
Error detected while processing /home2/e3003091/.vimrc:
line 2:
E185: Cannot find color scheme darkblue
line... (0 Replies)
Hi all Expertise,
I have following issue to solve,
SSL / TLS Renegotiation DoS (low) 222.225.12.13
Ease of Exploitation Moderate
Port 443/tcp
Family Miscellaneous
Following is the problem description:------------------
Description The remote service encrypts traffic using TLS / SSL and... (2 Replies)
Hi,
Whenever i try to open a file in any editor like vi, vim and nano i get this help.txt showing up in split screen without any key being pressed. This continues to pop up even when i close the help.txt. This behavior happens only when i am connected via putty. Is there a fix to this issue?
... (1 Reply)
Discussion started by: sunil0391
1 Replies
LEARN ABOUT DEBIAN
rdup-tr
RDUP-TR(1) rdup RDUP-TR(1)NAME
rdup-tr - transform rdup output
SYNOPSIS
rdup-tr [OPTION]...
DESCRIPTION
Transform rdup output into something else. Where something else can be a tar, cpio, pax archive or another rdup stream.
The rdup archive must be given on rdup-tr's standard input.
You can select multiple types of output (-O flag), but you must be aware that you may loose some information in formats other than rdup's
own, see the table below.
You may also supply rdup-tr with only a list of pathnames, this can be selected with the -L flag.
The following table shows what happens with the output depending on the input.
0 OK
D delete information is lost
H hardlink information is lost
| |
output | tar,cpio,pax | rdup
input | |
------------- | ------------- | ------
rdup | D | 0
filelist | DH | H
| |
OPTIONS -L Select list input format. Normally rdup-tr accepts rdup output, with this option you can give it a list of path names. Note: with
list input rdup-tr will `stat()` each file.
-O Output format. This can be 'tar', 'cpio', 'pax' or 'rdup'. It defaults to 'rdup'.
-X key Read the encryption key from the file key and encrypt all paths with Blowfish and this key and iv. After the encryption the binary
data is converted into ASCII using an URL safe (Section 4 of RFC 3548) version of base64 encode.
The encryption key must be on the first line and the key size must be 16 and 8 bytes for the iv, so 24 in total.
-Y key Read the decryption key from the file key and decrypt all paths with Blowfish and this key. Before the encryption the paths are con-
verted to binary by using an URL safe version of base64 decode.
-c Force output to the tty. Normally rdup-tr wants to see it's output redirected.
-v Be more verbose.
-V Print rdup-tr's version.
-h A short help.
EXAMPLES
The following is possible
rdup -Pgzip -Pmcrypt,-f,KEY,-c /dev/null /home |
rdup-tr -O tar -X<(echo secret) | gzip >
my-home-zipped-crypted-pathcrypted-tar.gz
That is: all files under /home are gzipped and encrypted on a per file basis (first line). Further more, all pathnames are Blowfish
encrypted (second line) with the key 'secret'. This is put in a tar file, which is then compressed, resulting in the final output (final
line).
Creating a compressed and encrypted tar archive out of a full rdup dump might be done as follows
rdup -Pgzip -Pmcrypt,-f,KEY,-c /dev/null /home |
rdup-tr -O tar > my-home-zipped-and-crypted.tar
Or even pack and unpack it on the fly
rdup -Pgzip -Pmcrypt,-fKEY,-c /dev/null /home | rdup-tr -Otar |
ssh user@remotehost tar xvCf /tmp -
Or encryption with openssl
rdup -Popenssl,enc,-e,-des-cbc,-k,secret /dev/null /home
Or, compressing with gzip, encrypting with openssl and then compressing the entire archive yet again
rdup -Pgzip -Popenssl,enc,-e,-des-cbc,-k,secret /dev/null /home |
gzip > my_compressed_encrypted_rdup_archive.gz
Recreating the original rdup output, which can be fed to rdup-up.
gunzip -c my_compressed_encrypted_rdup_archive.gz |
rdup-tr -Popenssl,enc,-d,-des-cbc,-k,secret -Pgzip,-d >
my_rdup_archive
rdup-up < my_rdup_archive -t /tmp/restore
Notice the reversal of the -P options.
EXIT CODE
rdup-tr return a zero exit code on success, otherwise 1 is returned.
AUTHOR
Written by Miek Gieben.
REPORTING BUGS
Report bugs to <miek@miek.nl>.
SEE ALSO
http:/www.miek.nl/projects/rdup/ is the main site of rdup. Also see rdup(1), rdup-up(1) and rdup-backups(7).
COPYRIGHT
Copyright (C) 2005-2010 Miek Gieben. This is free software. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
PURPOSE.
Licensed under the GPL version 3. See the file LICENSE in the source distribution of rdup.
1.1.11 27 Nov 2008 RDUP-TR(1)