mirror of
https://github.com/LCTT/TranslateProject.git
synced 2024-12-26 21:30:55 +08:00
TSL
This commit is contained in:
Xingyu Wang
parent
cb7a65bb51
commit
84865e5836
@ -1,236 +0,0 @@
|
|||||||
[#]: collector: (lujun9972)
|
|
||||||
[#]: translator: (wxy)
|
|
||||||
[#]: reviewer: ( )
|
|
||||||
[#]: publisher: ( )
|
|
||||||
[#]: url: ( )
|
|
||||||
[#]: subject: (7 Bash history shortcuts you will actually use)
|
|
||||||
[#]: via: (https://opensource.com/article/19/10/bash-history-shortcuts)
|
|
||||||
[#]: author: (Ian Miell https://opensource.com/users/ianmiell)
|
|
||||||
|
|
||||||
7 Bash history shortcuts you will actually use
|
|
||||||
======
|
|
||||||
Save time on the command line with these essential Bash shortcuts.
|
|
||||||
![Command line prompt][1]
|
|
||||||
|
|
||||||
Most guides to Bash history shortcuts exhaustively list every single one available. The problem with that is I would use a shortcut once, then glaze over as I tried out all the possibilities. Then I'd move onto my working day and completely forget them, retaining only the well-known [**!!** trick][2] I learned when I first started using Bash.
|
|
||||||
|
|
||||||
So most of them were never committed to memory.
|
|
||||||
|
|
||||||
This article outlines the shortcuts I _actually use_ every day. It is based on some of the contents of my book, [_Learn Bash the hard way_][3]; (you can read a [preview][4] of it to learn more).
|
|
||||||
|
|
||||||
When people see me use these shortcuts, they often ask me, "What did you do there!?" There's minimal effort or intelligence required, but to really learn them, I recommend using one each day for a week, then moving to the next one. It's worth taking your time to get them under your fingers, as the time you save will be significant in the long run.
|
|
||||||
|
|
||||||
### 1\. The "last argument" one: !$
|
|
||||||
|
|
||||||
If you only take one shortcut from this article, make it this one. It substitutes in the last argument of the last command into your line.
|
|
||||||
|
|
||||||
Consider this scenario:
|
|
||||||
|
|
||||||
|
|
||||||
```
|
|
||||||
$ mv /path/to/wrongfile /some/other/place
|
|
||||||
mv: cannot stat '/path/to/wrongfile': No such file or directory
|
|
||||||
```
|
|
||||||
|
|
||||||
Ach, I put the **wrongfile** filename in my command. I should have put **rightfile** instead.
|
|
||||||
|
|
||||||
You might decide to retype the last command and replace wrongfile with rightfile completely. Instead, you can type:
|
|
||||||
|
|
||||||
|
|
||||||
```
|
|
||||||
$ mv /path/to/rightfile !$
|
|
||||||
mv /path/to/rightfile /some/other/place
|
|
||||||
```
|
|
||||||
|
|
||||||
and the command will work.
|
|
||||||
|
|
||||||
There are other ways to achieve the same thing in Bash with shortcuts, but this trick of reusing the last argument of the last command is one I use the most.
|
|
||||||
|
|
||||||
### 2\. The "_n_th argument" one: !:2
|
|
||||||
|
|
||||||
Ever done anything like this?
|
|
||||||
|
|
||||||
|
|
||||||
```
|
|
||||||
$ tar -cvf afolder afolder.tar
|
|
||||||
tar: failed to open
|
|
||||||
```
|
|
||||||
|
|
||||||
Like many others, I get the arguments to **tar** (and **ln**) wrong more often than I would like to admit.
|
|
||||||
|
|
||||||
[![xkcd comic][5]][6]
|
|
||||||
|
|
||||||
When you mix up arguments like that, you can run:
|
|
||||||
|
|
||||||
|
|
||||||
```
|
|
||||||
$ !:0 !:1 !:3 !:2
|
|
||||||
tar -cvf afolder.tar afolder
|
|
||||||
```
|
|
||||||
|
|
||||||
and your reputation will be saved.
|
|
||||||
|
|
||||||
The last command's items are zero-indexed and can be substituted in with the number after the **!:**.
|
|
||||||
|
|
||||||
Obviously, you can also use this to reuse specific arguments from the last command rather than all of them.
|
|
||||||
|
|
||||||
### 3\. The "all the arguments" one: !:1-$
|
|
||||||
|
|
||||||
Imagine I run a command like:
|
|
||||||
|
|
||||||
|
|
||||||
```
|
|
||||||
`$ grep '(ping|pong)' afile`
|
|
||||||
```
|
|
||||||
|
|
||||||
The arguments are correct; however, I want to match **ping** or **pong** in a file, but I used **grep** rather than **egrep**.
|
|
||||||
|
|
||||||
I start typing **egrep**, but I don't want to retype the other arguments. So I can use the **!:1$** shortcut to ask for all the arguments to the previous command from the second one (remember they’re zero-indexed) to the last one (represented by the **$** sign).
|
|
||||||
|
|
||||||
|
|
||||||
```
|
|
||||||
$ egrep !:1-$
|
|
||||||
egrep '(ping|pong)' afile
|
|
||||||
ping
|
|
||||||
```
|
|
||||||
|
|
||||||
You don't need to pick **1-$**; you can pick a subset like **1-2** or **3-9** (if you had that many arguments in the previous command).
|
|
||||||
|
|
||||||
### 4\. The "last but _n_" one: !-2:$
|
|
||||||
|
|
||||||
The shortcuts above are great when I know immediately how to correct my last command, but often I run commands _after_ the original one, which means that the last command is no longer the one I want to reference.
|
|
||||||
|
|
||||||
For example, using the **mv** example from before, if I follow up my mistake with an **ls** check of the folder's contents:
|
|
||||||
|
|
||||||
|
|
||||||
```
|
|
||||||
$ mv /path/to/wrongfile /some/other/place
|
|
||||||
mv: cannot stat '/path/to/wrongfile': No such file or directory
|
|
||||||
$ ls /path/to/
|
|
||||||
rightfile
|
|
||||||
```
|
|
||||||
|
|
||||||
I can no longer use the **!$** shortcut.
|
|
||||||
|
|
||||||
In these cases, I can insert a **-_n_:** (where _**n**_ is the number of commands to go back in the history) after the **!** to grab the last argument from an older command:
|
|
||||||
|
|
||||||
|
|
||||||
```
|
|
||||||
$ mv /path/to/rightfile !-2:$
|
|
||||||
mv /path/to/rightfile /some/other/place
|
|
||||||
```
|
|
||||||
|
|
||||||
Again, once you learn it, you may be surprised at how often you need it.
|
|
||||||
|
|
||||||
### 5\. The "get me the folder" one: !$:h
|
|
||||||
|
|
||||||
This one looks less promising on the face of it, but I use it dozens of times daily.
|
|
||||||
|
|
||||||
Imagine I run a command like this:
|
|
||||||
|
|
||||||
|
|
||||||
```
|
|
||||||
$ tar -cvf system.tar /etc/system
|
|
||||||
tar: /etc/system: Cannot stat: No such file or directory
|
|
||||||
tar: Error exit delayed from previous errors.
|
|
||||||
```
|
|
||||||
|
|
||||||
The first thing I might want to do is go to the **/etc** folder to see what's in there and work out what I've done wrong.
|
|
||||||
|
|
||||||
I can do this at a stroke with:
|
|
||||||
|
|
||||||
|
|
||||||
```
|
|
||||||
$ cd !$:h
|
|
||||||
cd /etc
|
|
||||||
```
|
|
||||||
|
|
||||||
This one says: "Get the last argument to the last command (**/etc/system**) and take off its last filename component, leaving only the **/etc**."
|
|
||||||
|
|
||||||
### 6\. The "the current line" one: !#:1
|
|
||||||
|
|
||||||
For years, I occasionally wondered if I could reference an argument on the current line before finally looking it up and learning it. I wish I'd done so a long time ago. I most commonly use it to make backup files:
|
|
||||||
|
|
||||||
|
|
||||||
```
|
|
||||||
$ cp /path/to/some/file !#:1.bak
|
|
||||||
cp /path/to/some/file /path/to/some/file.bak
|
|
||||||
```
|
|
||||||
|
|
||||||
but once under the fingers, it can be a very quick alternative to …
|
|
||||||
|
|
||||||
### 7\. The "search and replace" one: !!:gs
|
|
||||||
|
|
||||||
This one searches across the referenced command and replaces what's in the first two **/** characters with what's in the second two.
|
|
||||||
|
|
||||||
Say I want to tell the world that my **s** key does not work and outputs **f** instead:
|
|
||||||
|
|
||||||
|
|
||||||
```
|
|
||||||
$ echo my f key doef not work
|
|
||||||
my f key doef not work
|
|
||||||
```
|
|
||||||
|
|
||||||
Then I realize that I was just hitting the **f** key by accident. To replace all the **f**s with **s**es, I can type:
|
|
||||||
|
|
||||||
|
|
||||||
```
|
|
||||||
$ !!:gs/f /s /
|
|
||||||
echo my s key does not work
|
|
||||||
my s key does not work
|
|
||||||
```
|
|
||||||
|
|
||||||
It doesn't work only on single characters; I can replace words or sentences, too:
|
|
||||||
|
|
||||||
|
|
||||||
```
|
|
||||||
$ !!:gs/does/did/
|
|
||||||
echo my s key did not work
|
|
||||||
my s key did not work
|
|
||||||
```
|
|
||||||
|
|
||||||
### Test them out
|
|
||||||
|
|
||||||
Just to show you how these shortcuts can be combined, can you work out what these toenail clippings will output?
|
|
||||||
|
|
||||||
|
|
||||||
```
|
|
||||||
$ ping !#:0:gs/i/o
|
|
||||||
$ vi /tmp/!:0.txt
|
|
||||||
$ ls !$:h
|
|
||||||
$ cd !-2:h
|
|
||||||
$ touch !$!-3:$ !! !$.txt
|
|
||||||
$ cat !:1-$
|
|
||||||
```
|
|
||||||
|
|
||||||
### **Conclusion**
|
|
||||||
|
|
||||||
Bash can be an elegant source of shortcuts for the day-to-day command-line user. While there are thousands of tips and tricks to learn, these are my favorites that I frequently put to use.
|
|
||||||
|
|
||||||
If you want to dive even deeper into all that Bash can teach you, pick up my book, [_Learn Bash the hard way_][3] or check out my online course, [Master the Bash shell][7].
|
|
||||||
|
|
||||||
* * *
|
|
||||||
|
|
||||||
_This article was originally posted on Ian's blog, [Zwischenzugs.com][8], and is reused with permission._
|
|
||||||
|
|
||||||
--------------------------------------------------------------------------------
|
|
||||||
|
|
||||||
via: https://opensource.com/article/19/10/bash-history-shortcuts
|
|
||||||
|
|
||||||
作者：[Ian Miell][a]
|
|
||||||
选题：[lujun9972][b]
|
|
||||||
译者：[译者ID](https://github.com/译者ID)
|
|
||||||
校对：[校对者ID](https://github.com/校对者ID)
|
|
||||||
|
|
||||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
|
||||||
|
|
||||||
[a]: https://opensource.com/users/ianmiell
|
|
||||||
[b]: https://github.com/lujun9972
|
|
||||||
[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/command_line_prompt.png?itok=wbGiJ_yg (Command line prompt)
|
|
||||||
[2]: https://opensource.com/article/18/5/bash-tricks
|
|
||||||
[3]: https://leanpub.com/learnbashthehardway
|
|
||||||
[4]: https://leanpub.com/learnbashthehardway/read_sample
|
|
||||||
[5]: https://opensource.com/sites/default/files/uploads/tar_2x.png (xkcd comic)
|
|
||||||
[6]: https://xkcd.com/1168/
|
|
||||||
[7]: https://www.educative.io/courses/master-the-bash-shell
|
|
||||||
[8]: https://zwischenzugs.com/2019/08/25/seven-god-like-bash-history-shortcuts-you-will-actually-use/
|
|
||||||
@ -0,0 +1,223 @@
|
|||||||
|
[#]: collector: (lujun9972)
|
||||||
|
[#]: translator: (wxy)
|
||||||
|
[#]: reviewer: ( )
|
||||||
|
[#]: publisher: ( )
|
||||||
|
[#]: url: ( )
|
||||||
|
[#]: subject: (7 Bash history shortcuts you will actually use)
|
||||||
|
[#]: via: (https://opensource.com/article/19/10/bash-history-shortcuts)
|
||||||
|
[#]: author: (Ian Miell https://opensource.com/users/ianmiell)
|
||||||
|
|
||||||
|
7 个实用的操作 Bash 历史记录的快捷方式
|
||||||
|
======
|
||||||
|
|
||||||
|
> 这些必不可少的 Bash 快捷键可在命令行上节省时间。
|
||||||
|
|
||||||
|
![Command line prompt][1]
|
||||||
|
|
||||||
|
大多数介绍 Bash 历史记录的指南都详尽地列出了每个可用的快捷方式。这样做的问题是，你会对每个快捷方式都浅尝辄止，然后在尝试了那么多的快捷方式后就搞得目不暇接。而在开始工作时它们就全被丢在脑后，只记住了刚开始使用 Bash 时学到的 [!! 技巧][2]。
|
||||||
|
|
||||||
|
这些技巧大多数从未进入记忆当中。
|
||||||
|
|
||||||
|
本文概述了我每天实际使用的快捷方式。它基于我的书《[Bash 学习，艰难之旅][3]》中的某些内容（你可以阅读其中的[样章][4]以了解更多信息）。
|
||||||
|
|
||||||
|
当人们看到我使用这些快捷方式时，他们经常问我：“你做了什么！？”学习它们只需付出很少的精力或智力，但是要真正的学习，我建议一周用一天学一个，然后下次再继续学习一个。值得花时间让它们落在你的指尖下，因为从长远来看，节省的时间将很重要。
|
||||||
|
|
||||||
|
### 1、最后一个参数：`!$`
|
||||||
|
|
||||||
|
如果你仅想从本文中学习一种快捷方式，那就是这个。它会将最后一个命令的最后一个参数替换到你的命令行中。
|
||||||
|
|
||||||
|
看看这种情况：
|
||||||
|
|
||||||
|
```
|
||||||
|
$ mv /path/to/wrongfile /some/other/place
|
||||||
|
mv: cannot stat '/path/to/wrongfile': No such file or directory
|
||||||
|
```
|
||||||
|
|
||||||
|
啊哈，我在命令中写了错误的文件名 “wrongfile”，我应该用正确的文件名 “rightfile” 代替。
|
||||||
|
|
||||||
|
你可以重新键入上一个命令，并用 “rightfile” 完全替换 “wrongfile”。但是，你也可以键入：
|
||||||
|
|
||||||
|
```
|
||||||
|
$ mv /path/to/rightfile !$
|
||||||
|
mv /path/to/rightfile /some/other/place
|
||||||
|
```
|
||||||
|
|
||||||
|
这个命令也可以奏效。
|
||||||
|
|
||||||
|
在 Bash 中还有其他方法可以通过快捷方式实现相同的目的，但是重用上一条命令的最后一个参数的这种技巧是我最常使用的。
|
||||||
|
|
||||||
|
### 2、第 n 个参数：`!:2`
|
||||||
|
|
||||||
|
是不是干过像这样的事情：
|
||||||
|
|
||||||
|
```
|
||||||
|
$ tar -cvf afolder afolder.tar
|
||||||
|
tar: failed to open
|
||||||
|
```
|
||||||
|
|
||||||
|
像许多其他人一样，我经常搞错 `tar`（和 `ln`）的参数顺序。
|
||||||
|
|
||||||
|
![xkcd comic][5]
|
||||||
|
|
||||||
|
当你搞混了参数，你可以这样：
|
||||||
|
|
||||||
|
```
|
||||||
|
$ !:0 !:1 !:3 !:2
|
||||||
|
tar -cvf afolder.tar afolder
|
||||||
|
```
|
||||||
|
|
||||||
|
这样就不会出丑了。
|
||||||
|
|
||||||
|
上一个命令的各个参数的索引是从零开始的，并且可以用 `!:` 之后跟上该索引数字替换它。
|
||||||
|
|
||||||
|
显然，你也可以使用它来重用上一个命令中的特定参数，而不是所有参数。
|
||||||
|
|
||||||
|
### 3、全部参数：`!:1-$`
|
||||||
|
|
||||||
|
假设我运行了类似这样的命令：
|
||||||
|
|
||||||
|
```
|
||||||
|
$ grep '(ping|pong)' afile
|
||||||
|
```
|
||||||
|
|
||||||
|
参数是正确的。然而，我想在文件中匹配 “ping” 或 “pong”，但我使用的是 `grep` 而不是 `egrep`。
|
||||||
|
|
||||||
|
我开始输入 `egrep`，但是我不想重新输入其他参数。因此，我可以使用 `!:1$` 快捷方式来调取上一个命令的所有参数，从第二个（记住它们的索引从零开始，因此是 `1`）到最后一个（由 `$` 表示）。
|
||||||
|
|
||||||
|
```
|
||||||
|
$ egrep !:1-$
|
||||||
|
egrep '(ping|pong)' afile
|
||||||
|
ping
|
||||||
|
```
|
||||||
|
|
||||||
|
你不用必须用 `1-$` 选择全部参数；你也可以选择一个子集，例如 `1-2` 或 `3-9` （如果上一个命令中有那么多参数的话）。
|
||||||
|
|
||||||
|
### 4、倒数第 n 个：`!-2:$`
|
||||||
|
|
||||||
|
当我输错之后马上就知道该如何更正我的上一条命令时，上面的快捷键非常有用，但是我经常在原始命令之后运行别的命令，这意味着最后一条命令不再是我所要引用的命令。
|
||||||
|
|
||||||
|
例如，还是用之前的 `mv` 例子，如果我通过 `ls` 检查文件夹的内容来纠正我的错误：
|
||||||
|
|
||||||
|
```
|
||||||
|
$ mv /path/to/wrongfile /some/other/place
|
||||||
|
mv: cannot stat '/path/to/wrongfile': No such file or directory
|
||||||
|
$ ls /path/to/
|
||||||
|
rightfile
|
||||||
|
```
|
||||||
|
|
||||||
|
我就不能再使用 `!$` 快捷方式了。
|
||||||
|
|
||||||
|
在这些情况下，我可以在 `!` 之后插入 `-n`：（其中 `n` 是要在历史记录中回溯的命令数），以从较旧的命令取得最后的参数：
|
||||||
|
|
||||||
|
```
|
||||||
|
$ mv /path/to/rightfile !-2:$
|
||||||
|
mv /path/to/rightfile /some/other/place
|
||||||
|
```
|
||||||
|
|
||||||
|
同样，一旦你学会了它，你可能会惊讶于你需要使用它的频率。
|
||||||
|
|
||||||
|
### 5、进入文件夹：`!$:h`
|
||||||
|
|
||||||
|
从表面上看，这个看起来不太有用，但我每天要用它几十次。
|
||||||
|
|
||||||
|
想象一下，我运行的命令如下所示：
|
||||||
|
|
||||||
|
```
|
||||||
|
$ tar -cvf system.tar /etc/system
|
||||||
|
tar: /etc/system: Cannot stat: No such file or directory
|
||||||
|
tar: Error exit delayed from previous errors.
|
||||||
|
```
|
||||||
|
|
||||||
|
我可能要做的第一件事是转到 `/etc` 文件夹，查看其中的内容并找出我做错了什么。
|
||||||
|
|
||||||
|
我可以通过以下方法来做到这一点：
|
||||||
|
|
||||||
|
```
|
||||||
|
$ cd !$:h
|
||||||
|
cd /etc
|
||||||
|
```
|
||||||
|
|
||||||
|
这是说：“获取上一个命令的最后一个参数（`/etc/system`），并删除其最后的文件名部分，仅保留 `/ etc`。”
|
||||||
|
|
||||||
|
### 6、当前行：`!#:1`
|
||||||
|
|
||||||
|
多年以来，在我最终查找并学会之前，我有时候想知道是否可以在当前行引用一个参数。我多希望我能早早学会这个快捷方式。我经常常使用它制作备份文件：
|
||||||
|
|
||||||
|
```
|
||||||
|
$ cp /path/to/some/file !#:1.bak
|
||||||
|
cp /path/to/some/file /path/to/some/file.bak
|
||||||
|
```
|
||||||
|
|
||||||
|
但当我学会之后，它很快就被下面的快捷方式替代了……
|
||||||
|
|
||||||
|
### 7、搜索并替换：`!!:gs`
|
||||||
|
|
||||||
|
这将搜索所引用的命令，并将前两个 `/` 之间的字符替换为后两个 `/` 之间的字符。
|
||||||
|
|
||||||
|
假设我想告诉别人我的 `s` 键不起作用，而是输出了 `f`：
|
||||||
|
|
||||||
|
```
|
||||||
|
$ echo my f key doef not work
|
||||||
|
my f key doef not work
|
||||||
|
```
|
||||||
|
|
||||||
|
然后我意识到我只是偶然才按下了 `f` 键。要将所有 `f` 替换为 `s`，我可以输入：
|
||||||
|
|
||||||
|
```
|
||||||
|
$ !!:gs/f /s /
|
||||||
|
echo my s key does not work
|
||||||
|
my s key does not work
|
||||||
|
```
|
||||||
|
|
||||||
|
它不只对单个字符起作用。我也可以替换单词或句子：
|
||||||
|
|
||||||
|
```
|
||||||
|
$ !!:gs/does/did/
|
||||||
|
echo my s key did not work
|
||||||
|
my s key did not work
|
||||||
|
```
|
||||||
|
|
||||||
|
### 测试一下
|
||||||
|
|
||||||
|
为了向你展示如何组合这些快捷方式，你知道这些命令片段将输出什么吗？
|
||||||
|
|
||||||
|
```
|
||||||
|
$ ping !#:0:gs/i/o
|
||||||
|
$ vi /tmp/!:0.txt
|
||||||
|
$ ls !$:h
|
||||||
|
$ cd !-2:h
|
||||||
|
$ touch !$!-3:$ !! !$.txt
|
||||||
|
$ cat !:1-$
|
||||||
|
```
|
||||||
|
|
||||||
|
### 总结
|
||||||
|
|
||||||
|
对于日常的命令行用户，Bash 可以作为快捷方式的优雅来源。虽然有成千上万的技巧要学习，但这些是我经常使用的最喜欢的技巧。
|
||||||
|
|
||||||
|
如果你想更深入地了解 Bash 可以教给你的全部知识，请买本我的书，《[Bash 学习，艰难之旅][3]》，或查看我的在线课程《[精通 Bash shell][7]》。
|
||||||
|
|
||||||
|
* * *
|
||||||
|
|
||||||
|
本文最初发布在 Ian 的博客 [Zwischenzugs.com][8] 上，并经允许重复发布。
|
||||||
|
|
||||||
|
--------------------------------------------------------------------------------
|
||||||
|
|
||||||
|
via: https://opensource.com/article/19/10/bash-history-shortcuts
|
||||||
|
|
||||||
|
作者：[Ian Miell][a]
|
||||||
|
选题：[lujun9972][b]
|
||||||
|
译者：[wxy](https://github.com/wxy)
|
||||||
|
校对：[校对者ID](https://github.com/校对者ID)
|
||||||
|
|
||||||
|
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||||
|
|
||||||
|
[a]: https://opensource.com/users/ianmiell
|
||||||
|
[b]: https://github.com/lujun9972
|
||||||
|
[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/command_line_prompt.png?itok=wbGiJ_yg (Command line prompt)
|
||||||
|
[2]: https://opensource.com/article/18/5/bash-tricks
|
||||||
|
[3]: https://leanpub.com/learnbashthehardway
|
||||||
|
[4]: https://leanpub.com/learnbashthehardway/read_sample
|
||||||
|
[5]: https://opensource.com/sites/default/files/uploads/tar_2x.png (xkcd comic)
|
||||||
|
[6]: https://xkcd.com/1168/
|
||||||
|
[7]: https://www.educative.io/courses/master-the-bash-shell
|
||||||
|
[8]: https://zwischenzugs.com/2019/08/25/seven-god-like-bash-history-shortcuts-you-will-actually-use/
|
||||||
Loading…
Reference in New Issue
Block a user