cW:change the Whole line from the current cursor position (same as C )
not quite: The difference is what "word" means. "cw" (or any other command using "w" as a range assignment) will treat special characters as the end of the word, whereas "cW" will treat only whitespace (or line ends) as word delimiters. In the following text:
if the cursor is under the "f" of "foo", then "cw" will replace "foo" with what you type afterwards, whereas "cW" will replace "foo=bar". To change the line from the cursor position to the line end use "C".
Hello there,
Is there anyway to make the tar utility print the contents of the files inside it (not list the files, but rather their contents) sequentially from the command line?
What I ultimately would like to do is to have a way of printing the contents of each file in the tar archive... (2 Replies)
1) I ran myScript with 2 arguments, I meant to use 3
if I do r my, it will rerun it with the 2 arguments. is there a way I can do r my and add a third argument at the end?
2) say I did
myAcript.ksh 2 5 7 8
I realise my typo. is there an easy way to redo the command replacing A with S?
... (4 Replies)
Discussion started by: JamesByars
4 Replies
3. Post Here to Contact Site Administrators and Moderators
What do you think could we open new top topic with tips and tricks and to show to other users some tricks what do we know like dtrace , new virtual server , how to add new users etc.
This is only suggestion (1 Reply)
I have a file which containd a string "old" and I need to replace all old with "new" if and only if it is a string not part of a string like Gold or fold etc.
I tried with sed like below
echo "old gold old" | sed 's/old/new/g'
It doesn't give the desired output, It give "old Gnew new".... (3 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)
I found a decent guide of VI basic tricks. This guide does expect you to have a decent understanding of VI. It does not go over very much beginner related.
vi Manual (3 Replies)
Discussion started by: cokedude
3 Replies
LEARN ABOUT LINUX
rollback_to_savepoint
ROLLBACK TO SAVEPOINT(7) SQL Commands ROLLBACK TO SAVEPOINT(7)NAME
ROLLBACK TO SAVEPOINT - roll back to a savepoint
SYNOPSIS
ROLLBACK [ WORK | TRANSACTION ] TO [ SAVEPOINT ] savepoint_name
DESCRIPTION
Roll back all commands that were executed after the savepoint was established. The savepoint remains valid and can be rolled back to again
later, if needed.
ROLLBACK TO SAVEPOINT implicitly destroys all savepoints that were established after the named savepoint.
PARAMETERS
savepoint_name
The savepoint to roll back to.
NOTES
Use RELEASE SAVEPOINT [release_savepoint(7)] to destroy a savepoint without discarding the effects of commands executed after it was estab-
lished.
Specifying a savepoint name that has not been established is an error.
Cursors have somewhat non-transactional behavior with respect to savepoints. Any cursor that is opened inside a savepoint will be closed
when the savepoint is rolled back. If a previously opened cursor is affected by a FETCH command inside a savepoint that is later rolled
back, the cursor position remains at the position that FETCH left it pointing to (that is, FETCH is not rolled back). Closing a cursor is
not undone by rolling back, either. A cursor whose execution causes a transaction to abort is put in a cannot-execute state, so while the
transaction can be restored using ROLLBACK TO SAVEPOINT, the cursor can no longer be used.
EXAMPLES
To undo the effects of the commands executed after my_savepoint was established:
ROLLBACK TO SAVEPOINT my_savepoint;
Cursor positions are not affected by savepoint rollback:
BEGIN;
DECLARE foo CURSOR FOR SELECT 1 UNION SELECT 2;
SAVEPOINT foo;
FETCH 1 FROM foo;
?column?
----------
1
ROLLBACK TO SAVEPOINT foo;
FETCH 1 FROM foo;
?column?
----------
2
COMMIT;
COMPATIBILITY
The SQL standard specifies that the key word SAVEPOINT is mandatory, but PostgreSQL and Oracle allow it to be omitted. SQL allows only
WORK, not TRANSACTION, as a noise word after ROLLBACK. Also, SQL has an optional clause AND [ NO ] CHAIN which is not currently supported
by PostgreSQL. Otherwise, this command conforms to the SQL standard.
SEE ALSO
BEGIN [begin(7)], COMMIT [commit(7)], RELEASE SAVEPOINT [release_savepoint(7)], ROLLBACK [rollback(7)], SAVEPOINT [savepoint(7)]
SQL - Language Statements 2010-05-14 ROLLBACK TO SAVEPOINT(7)