mirror of
https://github.com/LCTT/TranslateProject.git
synced 2025-01-16 22:42:21 +08:00
Merge remote-tracking branch 'LCTT/master'
This commit is contained in:
Xingyu Wang
commit
f80c91f8e3
@ -1,39 +1,37 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: (geekpi)
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
[#]: reviewer: (wxy)
|
||||
[#]: publisher: (wxy)
|
||||
[#]: url: (https://linux.cn/article-12076-1.html)
|
||||
[#]: subject: (Oracle Announces Java 14! How to Install it on Ubuntu Linux)
|
||||
[#]: via: (https://itsfoss.com/java-14-ubuntu/)
|
||||
[#]: author: (Ankush Das https://itsfoss.com/author/ankush/)
|
||||
|
||||
Oracle 发布 Java 14！如何在 Ubuntu Linux 上安装
|
||||
如何在 Ubuntu Linux 上安装 Oracle Java 14
|
||||
======
|
||||
|
||||
最近，Oracle 宣布 Java 14（或 Oracle JDK 14）正式开放。如果你想进行最新的实验或者开发的话，那么你可以试试在 Linux 系统上安装 Java 14。
|
||||
|
||||
|
||||
Oracle JDK 14（或简称 Java 14）[发行版][1]包含几个新功能，如果你想预览它们的话。我已添加了链接：
|
||||
最近，Oracle 宣布 Java 14（或 Oracle JDK 14）公开可用。如果你想进行最新的实验或者开发的话，那么你可以试试在 Linux 系统上安装 Java 14。
|
||||
|
||||
Oracle JDK 14（或简称 Java 14）[发布版][1]包含几个新功能，如果你想预览它们的话。我已添加了链接：
|
||||
|
||||
* [instanceof 的模式匹配][2]
|
||||
* [Records][3]
|
||||
* [Text Blocks][4]
|
||||
|
||||
|
||||
|
||||
除预览功能外，它还包含一些改进和补充。在新闻中，他们还提到了其他改进：
|
||||
|
||||
>此外，最新的 Java 版本增加了 Java 语言对 switch 表达式的支持，新增了用于持续监控 JDK Flight Recorder 数据的新 API，将低延迟 zgc 扩展到了 macOS 和 Windows，并添加在 incubator 模块中，独立的 Java 应用打包和为了安全的新的外部内存访问 API 来有效地访问 Java 堆外部的内存。
|
||||
> 此外，最新的 Java 版本增加了 Java 语言对 switch 表达式的支持，新增了用于持续监控 JDK Flight Recorder 数据的新 API，将低延迟 zgc 扩展到了 macOS 和 Windows，并添加在 incubator 模块中，独立的 Java 应用打包，以及为了安全、有效地访问 Java 堆外部内存的新的外部内存访问 API。
|
||||
|
||||
当然，如果你想详细了解细节，那么你应查看[官方公告][1]。
|
||||
当然，如果你想深入了解细节，那么你应查看[官方公告][1]。
|
||||
|
||||
在本教程中，我将向你展示在 Ubuntu 系统上安装 Java 14 的简便方法。继续阅读。
|
||||
在本教程中，我将向你展示在 Ubuntu 系统上安装 Java 14 的简便方法。请继续阅读。
|
||||
|
||||
**注意：**如果你选择 Oracle Java 11 或更高版本，那么应该了解新的 [Oracle 技术网络许可协议][5]，以了解它如何影响个人用户、开发人员和商业组织。通常，它们可以免费用于开发和测试，但不能用于生产。
|
||||
**注意：**如果你选择使用 Oracle Java 11 或更高版本，那么应该了解新的 [Oracle 技术网络许可协议][5]，以了解它如何影响个人用户、开发人员和商业组织。通常，它们可以免费用于开发和测试，但不能用于生产环境。
|
||||
|
||||
### 如何在 Ubuntu Linux 上安装 Java 14？
|
||||
|
||||
![][6]
|
||||
|
||||
作为参考，我已成功在默认安装 **OpenJDK 11** 的 **Pop!_OS 19.10** 上成功安装了它。
|
||||
|
||||
这里，我们将使用 [Linux Uprising][7] 的 Java 14 安装程序（最初基于 WebUpd8 Java 软件包）。
|
||||
@ -56,7 +54,7 @@ sudo apt install oracle-java14-set-default
|
||||
|
||||
### 总结
|
||||
|
||||
当然，这些是最新的特性，如果你不想破环环境，你或许会希望继续使用 Java11。如果你想在了解风险的情况下进行试验，请继续尝试！
|
||||
当然，这些会带来最新的特性，如果你不想破环原有环境，你或许会希望继续使用 Java 11。如果你想在了解风险的情况下进行试验，请继续尝试！
|
||||
|
||||
欢迎在下面的评论中让我知道你对 Java 14 的想法。
|
||||
|
||||
@ -67,7 +65,7 @@ via: https://itsfoss.com/java-14-ubuntu/
|
||||
作者：[Ankush Das][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[geekpi](https://github.com/geekpi)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
校对：[wxy](https://github.com/wxy)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
156
published/20200331 5 ways to level up your Vim skills.md
Normal file
156
published/20200331 5 ways to level up your Vim skills.md
Normal file
@ -0,0 +1,156 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: (wxy)
|
||||
[#]: reviewer: (wxy)
|
||||
[#]: publisher: (wxy)
|
||||
[#]: url: (https://linux.cn/article-12077-1.html)
|
||||
[#]: subject: (5 ways to level up your Vim skills)
|
||||
[#]: via: (https://opensource.com/article/20/3/vim-skills)
|
||||
[#]: author: (Detlef Johnson https://opensource.com/users/deckart)
|
||||
|
||||
提升你的 Vim 技能的 5 个方法
|
||||
======
|
||||
|
||||
> 通过一些有趣的小技巧使你的文本编辑器更上一层楼。
|
||||
|
||||
|
||||
|
||||
Vim 是最受欢迎的文本编辑器之一，因此绝对值得你花时间去学习如何使用它。就算你只是学习使用这个无处不在的 [Vi(m)][2] 命令行文本编辑器打开文件、输入和编辑一些文本、保存编辑的文件并退出程序，你都会受益匪浅。
|
||||
|
||||
你会发现，使用 Vim 非常方便的的场景几乎总是涉及到运行远程 Shell 操作的任务。如果你时不时地使用 ssh，比如
|
||||
|
||||
```
|
||||
$ ssh user@hostname.provider.com
|
||||
```
|
||||
|
||||
并在虚拟专用服务器（VPS）或本地虚拟化容器中工作，那么就可以从这些强大的 Vim 技能中受益匪浅。
|
||||
|
||||
### 将 Vim 设置为默认的文本编辑器
|
||||
|
||||
几乎所有的现代 Linux（或 BSD）发行版中，都可以在终端仿真器的 shell 命令提示符下使用 Vim。一旦在你的用户 shell 程序中将 Vim 定义为默认编辑器后，那么就可以使用熟悉的 Vim 键绑定来在内置的实用程序（例如 `man`）中导航。我将说明如何使用 Bash 和 Z shell（zsh）来实现此目的，zsh 现在是 macOS 用户的默认 shell（自 Catalina 起）。
|
||||
|
||||
#### 在 Bash 中将 Vim 设置为默认
|
||||
|
||||
Bash 通过点文件的组合来管理设置。最常见的的做法将你的编辑器添加到主目录中的 `.bashrc` 文件中，但也可以将其添加到 `.bash_profile` 中。（请阅读 [GNU Bash 文档][3]了解两者的不同之处）。
|
||||
|
||||
通过在 `~/.bashrc` 中添加以下内容，将 Vim 设置为默认编辑器：
|
||||
|
||||
```
|
||||
# set default editor to Vim
|
||||
export EDITOR=vim
|
||||
```
|
||||
|
||||
以 `#` 开头的行是可选的注释，这是一个好方法，可以提醒自己该命令的作用。
|
||||
|
||||
#### 在 zsh 中将 Vim 设置为默认
|
||||
|
||||
zsh 是一种越来越流行的终端仿真器，尤其是在苹果公司的基于 FreeBSD 的 Darwin 系统最近从 Bash 转向 zsh 以来。
|
||||
|
||||
zsh 点文件与 Bash 的文件相当，因此你可以在 `~/.zshrc` 或 `~/.zprofile` 之间进行选择。有关何时使用哪一个的详细信息，请参见 [zsh文档][4]。
|
||||
|
||||
将其设置为默认：
|
||||
|
||||
```
|
||||
# set default editor to Vim
|
||||
export EDITOR=vim
|
||||
```
|
||||
|
||||
### 优化 Vim 配置
|
||||
|
||||
Vim 像是终端仿真器 shell 一样，也使用点文件来设置个人偏好。如果你发现了这种模式，则可能已经猜到它是 `~/.vimrc`。
|
||||
|
||||
你可能要更改的第一个设置是将对传统的 Vi 兼容模式切换为“关闭”。由于 Vim 是 Vi 的超集，因此 Vi 中的所有功能在 Vim 中都是可用的，并且在 Vim 中得到了很大的改进，你可以获得许多高级功能。最新版本（8.2）允许你在分割的窗口中以子进程 shell 的方式打开一个终端。
|
||||
|
||||
顺便说一句，明确关闭对传统的 Vi 的兼容性看起来没有什么作用（[事实上，可能并没有什么作用][5]）。当 Vim 遇到 `.vimrc` 文件时，它会暗暗地自动将兼容模式切换到关闭。但有时将其明确关闭仍然很重要。缩写 `nocp` 是 `nocompatible` 的同义词，作用是一样的。[条条大道通罗马][6]，切换首选项有很多方式。
|
||||
|
||||
在 `.vimrc` 语法中， 以 `"` 开头的行是注释（就像 `.bashrc` 文件中的 `#` 一样），这些注释可以帮助你记住诸如为何选择了一个隐晦的设置名称之类的内容。
|
||||
|
||||
要关闭 Vi 兼容性，请将以下内容添加到 `~/.vimrc` 文件中：
|
||||
|
||||
```
|
||||
" ensure that legacy compatibility mode is off
|
||||
" documentation: <http://vimdoc.sourceforge.net/htmldoc/options.html\#'compatible>'
|
||||
set nocp
|
||||
```
|
||||
|
||||
### 理解模式
|
||||
|
||||
Vim 的 “模式”概念是非常重要的，尤其是“普通模式”和“插入模式”之间的区别。对模式的混淆是大多数新用户的困扰。模式并不是 Vim 所独有的，甚至也不是 Vi 所引入的。命令模式是如此的古老，以至于它比 70 年代发明的[复制和粘贴][7]功能还要早。
|
||||
|
||||
#### 重要的模式
|
||||
|
||||
Vim 依赖于不同的模式来定义键盘的敲击行为。需要了解的重要模式有：
|
||||
|
||||
* 普通模式：默认模式，主要用于导航和打开文件。
|
||||
* 插入模式（包括替换）：这种模式下 Vim 允许将文本输入到打开的文件中。
|
||||
* 可视模式：Vim 的行为类似于基于鼠标的输入方式，如复制、编辑、替换等。
|
||||
* 命令模式（包括行模式、Ex 命令模式和末行模式）：是在 Vim 中做更多事情的强大方法。
|
||||
|
||||
每种模式都有很多值得探索的地方。使用 [Vimtutor][8]（`vimtutor`）可以交互式地学习移动光标、模式和在末行模式下运行 Ex 命令。一些不可缺少的生产力操作符包括：
|
||||
|
||||
操作符 | 说明
|
||||
--- | ---
|
||||
`:E` | 打开资源管理器，用于定位文件和目录。
|
||||
`.` | 重复上次的编辑操作。
|
||||
`;` | 向前重复上一次的动作或移动
|
||||
`,` | 向后重复上一次的动作或移动。
|
||||
`/` | 向前搜索文档。
|
||||
`?` | 向后搜索文档。
|
||||
`*` | 查找光标所在处的单词的下一个出现的地方。
|
||||
`#` | 查找光标所在处的单词的上一次出现的地方。
|
||||
`~` | 切换大小写。
|
||||
`%` | 在 `()`、`[]` 和 `{}` 的开闭符号之间切换；对编码非常有用。
|
||||
`z=` | 提出拼写建议。
|
||||
|
||||
### 像钢琴一样弹奏 Vim
|
||||
|
||||
尽管把 Vim 的操作符“语言”记在记忆中是很重要的，但要想掌握它，难点在于学会像音乐家一样思考，把操作符和动作组合成“和弦”，这样你就可以像弹钢琴一样弹奏 Vim。这就是 Vim 的文本操作能力可以与另一个著名的命令行编辑器 Emacs 相媲美的地方。（虽然其中一个编辑器会让磨损掉你的 `Esc` 键，而另一个编辑器会让你的 `Ctrl` 键磨损掉。）
|
||||
|
||||
在描述键“和弦”时，Vim 中的传统做法是用大写字母 C 后面加上一个连字符（`C-`）来指代 `Ctrl` 键。这并不是通用的，但我将从这里开始遵循这一惯例，并在有可能引起混淆的时候加以说明。
|
||||
|
||||
如果你在 Vim 中键入长行，你会想把它设置成可以换行。想要根据你的工作方式对 Vim 进行个性化设置，请考虑一下这个设置：默认情况下，你希望 Vim 启动时如何处理文本换行？开还是关？我喜欢将其关闭，并将其留在运行命令文件之外。当我想让文本自动换行时，我只需在命令行模式下用 `:set wrap` 设置即可。
|
||||
|
||||
让 Vim 设置为默认情况下自动换行并没有错，这只是一个偏好问题 —— 它可能随着时间的推移而改变。同样你也可以控制粘贴、代码语言缩进语法和 `Tab` 键的设置（制表符还是空格？多少个空格？可也在[这里][9]深入研究这些选项）。所有这些默认行为的选项都是完全可配置和可更改的，并且在你使用命令行模式操作时可以实时更改。
|
||||
|
||||
你会在社区论坛、Vim 维基和文章（比如这篇文章）中找到很多关于设置 Vim 默认设置的建议。你应该很熟悉为你的个人计算环境设置首选项，Vim 也不例外。我强烈建议你从对设置进行很小的更改开始，慢慢地进行其它更改，以便你可以轻松地恢复设置。这样一来，你就可以好多年避免使用插件或完全不用插件。
|
||||
|
||||
### Vim 8.2 中的分割、标签和终端
|
||||
|
||||
有两种方法可以将你正在处理的文件分割成不同的视图：它们可以并排显示，也可以使用应用程序标签页在全屏（窗口）中切换。这些对应用程序窗口的更改是从命令模式启动的，这需要使用冒号（`:`）来调起提示符。
|
||||
|
||||
每个分割的窗口可以容纳一个文件进行编辑，你可以通过标签页在更多的文件之间随意切换。分割的屏幕空间有限，所以当你想分割更多的屏幕时，标签页是很方便的。想要如何设置，纯属个人喜好的问题。要水平分割一个窗口，使用 `:sp`，垂直分割时使用 `:vs`。
|
||||
|
||||
从 [Vim 8.2][10] 开始，你可以用 `:vert term` 打开一个垂直分割的终端 shell 子进程，以在你的代码旁边的命令行上进行操作。你需要键入 `exit` 来关闭你的终端进程，就像你结束一个 shell 会话一样，但你关闭这个分割的窗口和标签页的方式和关闭任何普通的 Vim 窗口一样，要用 `:q` 来关闭。
|
||||
|
||||
要初始化一个标签页，请使用一个特殊的编辑命令：`:tabedit`，它会自动切换到新打开的标签页。如果你给该命令一个文件名作为参数，会打开该文件并进行编辑。如果你忽略了给它一个文件名作为参数，可以在命令行模式下的使用编辑命令 `:e filename.txt`，就像在任何一个普通的 Vim 窗口中一样。可以使用下一个（`:tabn`）和上一个（`:tabp`）命令在标签页间导航。
|
||||
|
||||
要使用分割，你需要知道如何使用组合键 `C-w` 和你想要移动的方向的移动键，例如左（`h`）、下（`j`）、左（`k`）、右（`l`）。如果你想学习更多的组合键，请阅读 Vim 手册中的 `:help split` 和 `:help tabpage`。
|
||||
|
||||
### 获取帮助
|
||||
|
||||
虽然可以在 Vimtutor 中打开参考 Vim 手册，但用 `:help` 打开 Vim 帮助，可以让你自己把时间花在编辑器上，不用完全依赖像这样的文章，就能获得更多的成果。经验是掌握 Vim 的关键。经验有助于提高你的整体计算直觉，因为 Vim 中的很多东西都是从 Unix 宇宙中汲取的。
|
||||
|
||||
祝你在探索 Vim 之美的过程中玩得开心，有什么问题可以在评论中分享。
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/20/3/vim-skills
|
||||
|
||||
作者：[Detlef Johnson][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[wxy](https://github.com/wxy)
|
||||
校对：[wxy](https://github.com/wxy)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://opensource.com/users/deckart
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/keyboaord_enter_writing_documentation.jpg?itok=kKrnXc5h (Computer keyboard typing)
|
||||
[2]: https://www.vim.org/
|
||||
[3]: https://www.gnu.org/software/bash/manual/html_node/Bash-Startup-Files.html
|
||||
[4]: http://zsh.sourceforge.net/Intro/intro_3.html
|
||||
[5]: http://vimdoc.sourceforge.net/htmldoc/starting.html#compatible-default
|
||||
[6]: https://en.wikipedia.org/wiki/There%27s_more_than_one_way_to_do_it
|
||||
[7]: https://www.npr.org/2020/02/22/808404858/remembering-the-pioneer-behind-your-computers-cut-copy-and-paste-functions
|
||||
[8]: http://www2.geog.ucl.ac.uk/~plewis/teaching/unix/vimtutor
|
||||
[9]: https://opensource.com/article/18/9/vi-editor-productivity-powerhouse
|
||||
[10]: https://www.vim.org/vim-8.2-released.php
|
||||
106
sources/talk/20200405 Book review- Nine Lies About Work.md
Normal file
106
sources/talk/20200405 Book review- Nine Lies About Work.md
Normal file
@ -0,0 +1,106 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: ( )
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
[#]: subject: (Book review: Nine Lies About Work)
|
||||
[#]: via: (https://opensource.com/open-organization/20/4/book-review-nine-lies-about-work)
|
||||
[#]: author: (Ron McFarland https://opensource.com/users/ron-mcfarland)
|
||||
|
||||
Book review: Nine Lies About Work
|
||||
======
|
||||
An examination of common work misconceptions and how open organizations
|
||||
are often ahead of the curve.
|
||||
![Carrot on a stick][1]
|
||||
|
||||
In _Nine Lies About Work_, authors Marcus Buckingham and Ashley Goodall examine what we might consider "common theories" about aspects of contemporary organizational life—and they debunk those theories. The book's so-called "lies" are, therefore, not really lies but rather common beliefs about work that simply aren't accurate in actual working environments today.
|
||||
|
||||
In this review, I'll outline all nine of those misconceptions and explain what the authors believe is really true in the case of each one. But then I'll focus more on explaining the misconceptions that are especially relevant to [open organizations][2].
|
||||
|
||||
### Liar, liar
|
||||
|
||||
Buckingham and Goodall address the following nine "lies" about work.
|
||||
|
||||
Lie #1—People care about which company they work for. The authors believe that people really care about which team they're directly working on. That is where we [find engagement][3].
|
||||
|
||||
Lie #2—The best plan wins. The authors believe that the best front-line intelligence and feedback wins. In this rapidly changing world, [plans only tell you where you are now][4] and where you may be in the very near future (that is, in a few weeks or months).
|
||||
|
||||
Lie #3—The best companies cascade goals. The authors believe that the best companies [disseminate downward meaning][5] (that is, public purpose) to their staff.
|
||||
|
||||
Lie #4—The best people are well-rounded. The authors believe that the best people are good only at specific tasks (and not _necessarily_ other tasks).
|
||||
|
||||
Lie #5—People need feedback. The authors believe that people need nonjudgmental, uncritical attention, and to be recognized; they don't need criticism.
|
||||
|
||||
Lie #6—People can reliably rate other people. The authors believe that people can reliably rate their own experience and [evaluate their own performance][6] often better than others can.
|
||||
|
||||
Lie #7—People have potential. The authors believe that every person possesses individual needs and individual feelings of forward momentum and progress. Therefore, their potential cannot be determined.
|
||||
|
||||
Lie #8—Work-life balance matters most. The authors believe that love-in-work matters most. Companies should promote each individual finding the [love of what they do at work][7], then expand on that love. Companies should promote having fun at work, but they rarely do.
|
||||
|
||||
Lie #9—Leadership is a thing. The authors believe that [we each follow people with a vision][8] in which we believe. To say a person is "a good leader" is, therefore, only situational according to individual followers. No universal criteria, rule, or model for effective leadership exists.
|
||||
|
||||
### Teams over companies
|
||||
|
||||
Now let's take a hard look at Lie #1. The authors believe that someone seeking a job will care about the quality of a company, their status inside that company, and their pay, but as soon as work begins, team engagement becomes far more important to them. That's because teams focus on what we do on a daily basis. Those teams might even be unofficial groups inside an organization—"[internal communities][9]," we might call them. Buckingham and Goodall provide eight characteristics of great teams, and these characteristics would ring equally true in [open organization communities][2]. The authors present them separated into two categories—"We"-related and "Me"-related):
|
||||
|
||||
* The members are enthusiastic about the team mission ("We").
|
||||
* Each is surrounded by people who share the same values ("We").
|
||||
* Their teammates will stand behind them when needed ("We")
|
||||
* The members feel confident regarding the future of the company ("We").
|
||||
* Each member understands what is expected ("Me").
|
||||
* Everyone feels they have a chance to use their particular strengths ("Me"). According to a 2018 study from ADP Research Institute, cited in the book's appendix, if we can use our strengths that bring us joy and energizes us 20% of the time at work, total work engagement skyrockets.
|
||||
* All members can be recognized for excellent work ("Me").
|
||||
* The members are challenged to grow ("Me").
|
||||
|
||||
|
||||
|
||||
All these characteristics describe a healthy culture in an open organization community.
|
||||
|
||||
According to the authors, a company should explore what [informal, unofficial teams][10] it has and learn what they're involved in. Usually, they say, the average person is on five teams, each with different purposes. Ask people if they have these types of teams (or a single mentor) with whom they can consult inside the company. Larger, more formal groups are less important.
|
||||
|
||||
More important, however, are lunch meetings between informal team members or chats in corners discussing how they can help each other. When I was providing sales seminars, for example, I would walk around the company cafeteria and have these discussions with global sales departments. By doing this, I developed strong communities over a 20-year period. The quality and quantities of these teams are directly connected to employee engagement and are extremely important to the success of a company, according to the authors. An organizational leader's primary job is to create an environment where these teams can grow and thrive.
|
||||
|
||||
### Forget planning
|
||||
|
||||
Next, let's turn to Lie #2: the best plan wins. Buckingham and Goodall believe the best front-line intelligence wins. Open organizations [rely a great deal on bottom-up management techniques][11], which fits nicely into what the authors are saying here. All the action is on the front-line, and real-time reporting to management on situational developments is extremely important, according to the authors. Conditions are changing so fast that [by the time some plans are introduced, they are already out-of-date][12]. That is why open organizations strongly believe in cultivating ground-level decision-making practices. People closest to the issues know what's happening.
|
||||
|
||||
Regarding [open organization principles][2], we might note the emphasis on getting front-line information in real-time and broadly distributing it as much as possible (inclusivity, transparency, broader community), as well as encouraging and reporting front-line suggestions (collaboration, adaptability). Communication is two-way. To share information efficiently and understand when it's needed, Buckingham and Goodall believe that many small, short, frequent meetings are always more productive than large, long, infrequent ones.
|
||||
|
||||
### Don't judge
|
||||
|
||||
Next, let's examine Lie #5: People need feedback. The authors do recognize people's need for nonjudgmental, uncritical attention, and their desire to be recognized. A leader's level of uncritical attention is directly connected to the level of staff engagement. Just asking, "[How are you doing in your work?][13]" and "Well, how can I help?" is all that is needed.
|
||||
|
||||
The authors believe that the worst managers are those that ignore people. Average managers don't ignore people, but they give negative feedback, which weakens their teams' feelings of engagement. The best managers, team leaders, or community leaders don't ignore and don't judge. At least weekly, they simply ask questions and provide help if needed. A high degree of managerial attention directly improves front-line engagement. The authors believe that it makes members feel connected, supported, and understood.
|
||||
|
||||
Buckingham and Goodall believe that looking at a staff's negative qualities is a natural tendency. Therefore, leaders and managers must make strong efforts to avoid doing so. This effort is worth it, the authors argue, as it results in greater performance, engagement, and growth. For example, when I was giving sales manager training, I frequently needed to address the situation of handling sales staff coming to the manager to help them with a customer problem. I recommended that the manager just ask the sales staff a simple question: "What did you do and say when you met the customer, and what would you do differently if you could visit the customer all over again?" This forced salespeople to come up with their own advice.
|
||||
|
||||
### Concluding thoughts
|
||||
|
||||
_Nine Lies about Work_ has much to teach anyone interested in open organizations. Buckingham is a global researcher in human strengths development and performance; Goodall is a senior VP in leadership and team intelligence at Cisco. It is amazing how closely their beliefs align with open organization principles. The ways they articulate those beliefs in this book are enlightening.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/open-organization/20/4/book-review-nine-lies-about-work
|
||||
|
||||
作者：[Ron McFarland][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/ron-mcfarland
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/BUSINESS_pink2.png?itok=I5Wgct6V (Carrot on a stick)
|
||||
[2]: https://opensource.com/open-organization/resources/open-org-definition
|
||||
[3]: https://opensource.com/open-organization/18/10/understanding-engagement-empowerment
|
||||
[4]: https://opensource.com/open-organization/19/5/planning-future-unknowable
|
||||
[5]: https://opensource.com/open-organization/18/7/culture-of-experimentation-in-4-steps
|
||||
[6]: https://opensource.com/open-organization/15/5/measuring-performance-open-source-way
|
||||
[7]: https://opensource.com/open-organization/15/11/reigniting-employee-passion
|
||||
[8]: https://opensource.com/open-organization/18/12/what-is-open-leadership
|
||||
[9]: https://opensource.com/open-organization/19/11/what-is-community-practice
|
||||
[10]: https://opensource.com/open-organization/20/1/why-build-community-of-practice
|
||||
[11]: https://opensource.com/open-organization/17/3/making-better-open-decisions
|
||||
[12]: https://opensource.com/open-organization/18/3/try-learn-modify
|
||||
[13]: https://opensource.com/open-organization/16/10/how-ask-why-without-upsetting-anyone
|
||||
@ -1,5 +1,5 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: ( )
|
||||
[#]: translator: (robsean)
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
|
||||
@ -1,164 +0,0 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: (robsean)
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
[#]: subject: (Use the Fluxbox Linux desktop as your window manager)
|
||||
[#]: via: (https://opensource.com/article/19/12/fluxbox-linux-desktop)
|
||||
[#]: author: (Seth Kenlon https://opensource.com/users/seth)
|
||||
|
||||
Use the Fluxbox Linux desktop as your window manager
|
||||
======
|
||||
This article is part of a special series of 24 days of Linux desktops.
|
||||
Fluxbox is very light on system resources, yet it has vital Linux
|
||||
desktop features to make your user experience easy, blazingly efficient,
|
||||
and unduly fast.
|
||||
![Text editor on a browser, in blue][1]
|
||||
|
||||
The concept of a desktop may differ from one computer user to another. Many people see the desktop as a home base, or a comfy living room, or even a literal desktop where they place frequently used notepads, their best pens and pencils, and their favorite coffee mug. KDE, GNOME, Pantheon (and so on) provide that kind of comfort on Linux.
|
||||
|
||||
But for some users, the desktop is just empty monitor space, a side effect of not yet having any free-floating application windows projected directly onto their retina. For these users, the desktop is a void over which they can run applications—whether big office and graphic suites, or a simple terminal window, or docked applets—to manage services. This model of operating a [POSIX][2] computer has a long history, and one branch of that family tree is the *box window managers: Blackbox, Fluxbox, and Openbox.
|
||||
|
||||
[Fluxbox][3] is a window manager for X11 systems that's based on an older project called Blackbox. Blackbox development was waning when I discovered Linux, so I fell into Fluxbox, and I've used it ever since on at least one of my active systems. It is written in C++ and is licensed under the MIT open source license.
|
||||
|
||||
### Installing Fluxbox
|
||||
|
||||
You are likely to find Fluxbox included in the software repository of your Linux distribution, but you can also find it on [Fluxbox.org][4]. If you're already running a different desktop, it's safe to install Fluxbox on the same system because Fluxbox doesn't predetermine any configuration or accompanying applications.
|
||||
|
||||
After installing Fluxbox, log out of your current desktop session so you can log into your new one. By default, your session manager (KDM, GDM, LightDM, or XDM, depending on your setup) will continue to log you into your previous desktop, so you must override that before logging in.
|
||||
|
||||
To override the desktop with GDM:
|
||||
|
||||
![Select your desktop session in GDM][5]
|
||||
|
||||
Or with KDM:
|
||||
|
||||
![Select your desktop session with KDM][6]
|
||||
|
||||
### Configuring the Fluxbox desktop
|
||||
|
||||
When you first log in, the screen is mostly empty because all Fluxbox provides are panels (for a taskbar, system tray, and so on) and window decoration for application windows.
|
||||
|
||||
![Default Fluxbox configuration on CentOS 7][7]
|
||||
|
||||
If your distribution delivers a plain Fluxbox desktop, you can set a background for your desktop using the **feh** command (you may need to install it from your distribution's repository). This command has a few options for setting the background, including **\--bg-fill** to fill the screen with your wallpaper of choice, **\--bg-scale** to scale it to fit, and so on.
|
||||
|
||||
|
||||
```
|
||||
`$ feh --bg-fill ~/photo/oamaru/leaf-spiral.jpg`
|
||||
```
|
||||
|
||||
![Fluxbox with a theme applied][8]
|
||||
|
||||
By default, Fluxbox auto-generates a menu, available with a right-click anywhere on the desktop, that gives you access to applications. Depending on your distribution, this menu may be very minimal, or it may list all the launchers in your **/usr/share/applications** directory.
|
||||
|
||||
Fluxbox configuration is set in text files, and those text files are contained in the **$HOME/.fluxbox** directory. You can:
|
||||
|
||||
* Set keyboard shortcuts in **keys**
|
||||
* Set startup services and applications in **startup**
|
||||
* Set desktop preferences (such as the number of workspaces, locations of panels, and so on) in **init**
|
||||
* Set menu items in **menu**
|
||||
|
||||
|
||||
|
||||
The text configuration files are easy to reverse-engineer, but you also can (and should) read the Fluxbox [documentation][9].
|
||||
|
||||
For example, this is my typical menu (or at least the basic structure of it):
|
||||
|
||||
|
||||
```
|
||||
# to use your own menu, copy this to ~/.fluxbox/menu, then edit
|
||||
# ~/.fluxbox/init and change the session.menuFile path to ~/.fluxbox/menu
|
||||
|
||||
[begin] (fluxkbox)
|
||||
[submenu] (apps) {}
|
||||
[submenu] (txt) {}
|
||||
[exec] (Emacs 23 (text\\)) { x-terminal-emulator -T "Emacs (text)" -e /usr/bin/emacs -nw} <>
|
||||
[exec] (Emacs (X11\\)) {/usr/bin/emacs} <>
|
||||
[exec] (LibreOffice) {/usr/bin/libreoffice}
|
||||
[end]
|
||||
[submenu] (code) {}
|
||||
[exec] (qtCreator) {/usr/bin/qtcreator}
|
||||
[exec] (eclipse) {/usr/bin/eclipse}
|
||||
[end]
|
||||
[submenu] (graphics) {}
|
||||
[exec] (ksnapshot) {/usr/bin/ksnapshot}
|
||||
[exec] (gimp) {/usr/bin/gimp}
|
||||
[exec] (blender) {/usr/bin/blender}
|
||||
[end]
|
||||
[submenu] (files) {}
|
||||
[exec] (dolphin) {/usr/bin/dolphin}
|
||||
[exec] (konqueror) { /usr/bin/kfmclient openURL $HOME }
|
||||
[end]
|
||||
[submenu] (network) {}
|
||||
[exec] (firefox) {/usr/bin/firefox}
|
||||
[exec] (konqueror) {/usr/bin/konqueror}
|
||||
[end]
|
||||
[end]
|
||||
## change window manager or work env
|
||||
[submenu] (environments) {}
|
||||
[restart] (flux) {/usr/bin/startfluxbox}
|
||||
[restart] (ratpoison) {/usr/bin/ratpoison}
|
||||
[exec] (openIndiana) {/home/kenlon/qemu/startSolaris.sh}
|
||||
[end]
|
||||
|
||||
[config] (config)
|
||||
[submenu] (styles) {}
|
||||
[stylesdir] (/usr/share/fluxbox/styles)
|
||||
[stylesdir] (~/.fluxbox/styles)
|
||||
[end]
|
||||
[workspaces] (workspaces)
|
||||
[reconfig] (reconfigure)
|
||||
[restart] (restart)
|
||||
[exit] (exeunt)
|
||||
[end]
|
||||
```
|
||||
|
||||
The menu also provides a few preference settings, such as the ability to pick a theme and restart or log out from your Fluxbox session.
|
||||
|
||||
I launch most applications using keyboard shortcuts, which are entered into the **keys** configuration file. Here are some examples (the **Mod4** key is the Super key, which I use to designate global shortcuts):
|
||||
|
||||
|
||||
```
|
||||
# open apps
|
||||
Mod4 t :Exec konsole
|
||||
Mod4 k :Exec konqueror
|
||||
Mod4 z :Exec fbrun
|
||||
Mod4 e :Exec emacs
|
||||
Mod4 f :Exec firefox
|
||||
Mod4 x :Exec urxvt
|
||||
Mod4 d :Exec dolphin
|
||||
Mod4 q :Exec xscreensaver-command -activate
|
||||
Mod4 3 :Exec ksnapshot
|
||||
```
|
||||
|
||||
Between these shortcuts and an open terminal, I have little use for a mouse during most of my workday, so there's no wasted time switching from one controller to another. And because Fluxbox stays well out of the way, there's little distraction.
|
||||
|
||||
### Why you should use Fluxbox
|
||||
|
||||
Fluxbox is very light on system resources, yet it has vital features to make your user experience easy, blazingly efficient, and unduly fast. It's simple to customize, and it allows you to define your own workflow. You don't have to use Fluxbox's panels, because there are other excellent panels out there. You can even middle-click and drag two separate application windows into one another so that they become one window, each in its own tab.
|
||||
|
||||
The possibilities are endless, so try the steady simplicity that is Fluxbox on your Linux box today!
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/19/12/fluxbox-linux-desktop
|
||||
|
||||
作者：[Seth Kenlon][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/seth
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/browser_blue_text_editor_web.png?itok=lcf-m6N7 (Text editor on a browser, in blue)
|
||||
[2]: https://opensource.com/article/19/7/what-posix-richard-stallman-explains
|
||||
[3]: http://fluxbox.org
|
||||
[4]: http://fluxbox.org/download/
|
||||
[5]: https://opensource.com/sites/default/files/advent-gdm_0.jpg (Select your desktop session in GDM)
|
||||
[6]: https://opensource.com/sites/default/files/advent-kdm.jpg (Select your desktop session with KDM)
|
||||
[7]: https://opensource.com/sites/default/files/advent-fluxbox-default.jpg (Default Fluxbox configuration on CentOS 7)
|
||||
[8]: https://opensource.com/sites/default/files/advent-fluxbox-green.jpg (Fluxbox with a theme applied)
|
||||
[9]: http://fluxbox.org/features/
|
||||
@ -1,135 +0,0 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: (HankChow)
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
[#]: subject: (How to Upgrade to Ubuntu 20.04 Beta from 18.04 & 19.10)
|
||||
[#]: via: (https://itsfoss.com/upgrade-ubuntu-beta/)
|
||||
[#]: author: (Abhishek Prakash https://itsfoss.com/author/abhishek/)
|
||||
|
||||
How to Upgrade to Ubuntu 20.04 Beta from 18.04 & 19.10
|
||||
======
|
||||
|
||||
[Ubuntu 20.04 LTS release][1] is less than a month away. It has plenty of visual changes and several performance improvements.
|
||||
|
||||
If you are still using Ubuntu 18.04 LTS, you’ll find Ubuntu 20.04 stunningly beautiful with its dark Yaru theme. Here’s a [video showing what Ubuntu 20.04 looks like][2]. Have a look and judge it yourself.
|
||||
|
||||
[Subscribe to our YouTube channel for more Linux videos][3]
|
||||
|
||||
Looks great, isn’t it? If you are excited about Ubuntu 20.04 and cannot wait till the final stable release on 23rd April, you can start using it even today. It’s fairly stable and it could even help Ubuntu team in testing this release.
|
||||
|
||||
There’s always the option to download the daily build and install it afresh. But if you are using Ubuntu 18.04 or Ubuntu 19.10, you can upgrade to Ubuntu 20.04 beta from your existing system.
|
||||
|
||||
Please check this tutorial to learn [how to find out which Ubuntu version you are using][4].
|
||||
|
||||
In this tutorial, I’ll show you the steps to upgrade to Ubuntu 20.04 beta.
|
||||
|
||||
### How to upgrade to Ubuntu 20.04 beta from Ubuntu 18.04 and 19.10
|
||||
|
||||
![Upgrade Ubuntu 20 04 Beta][5]
|
||||
|
||||
Before you see the steps, let me answer some of the common questions regarding upgrading to Ubuntu beta version.
|
||||
|
||||
* The upgrade from one version to another is an easy process but you need to have a good internet connection that could download a couple of GBs of data at a good speed.
|
||||
* Upgrading to a newer version disables the third-party repositories ([PPA][6] you added on your own). Some of these PPAs might not be available for the new version yet. You can manually enable the PPAs after upgrading.
|
||||
* Having a backup of your important data on an external USB disk is always recommended. Just copy all your important files from Documents, Pictures, Music, Downloads and other places and put it on an external USB or hard disk.
|
||||
* Once you have upgraded to a newer version, you cannot go back to the older version you were using. Reinstalling the older version is the only option.
|
||||
* If you upgrade to the Ubuntu 20.04 beta version, you don’t need to install it again when the final stable version is released. Just update your Ubuntu system regularly and you’ll already be using the same 20.04 when it is released.
|
||||
* You cannot upgrade to Ubuntu 20.04 directly from Ubuntu 16.04, 17, 18, 19.04.
|
||||
|
||||
|
||||
|
||||
Alright! You know enough now. Let’s see the steps to upgrade to Ubuntu 20.04 beta from Ubuntu 19.10 and 18.04.
|
||||
|
||||
#### Step 1: Make sure the settings are right
|
||||
|
||||
Go to Software & Updates application:
|
||||
|
||||
![Software & Updates application in Ubuntu][7]
|
||||
|
||||
In the Updates tab, check that Notify me of a new Ubuntu version is set to “Any new version” or “LTS version”:
|
||||
|
||||
![Ubuntu Upgrade Version Settings][8]
|
||||
|
||||
This may reload the Software repository cache.
|
||||
|
||||
#### Step 2: Update your system for any pending software updates
|
||||
|
||||
Once you have the correct settings in place, open a terminal ([use Ctrl+Alt+T shortcut in Ubuntu][9]) and use the following [command to update your Ubuntu system][10]:
|
||||
|
||||
```
|
||||
sudo apt update && sudo apt full-upgrade
|
||||
```
|
||||
|
||||
The apt full-upgrade or dist-upgrade function the same as ‘apt upgrade’ but it will remove currently installed packages if this is needed to upgrade the system as a whole (i.e. a version upgrade).
|
||||
|
||||
Your system may ask to restart after installing updates. That’s fine. Restart and resume upgrading to beta release from step 3.
|
||||
|
||||
#### Step 3: Run update manager with development release upgrade option
|
||||
|
||||
Now that you have all the necessary updates installed, you can open the update manager but with -d option. The -d option tells it to look for development releases.
|
||||
|
||||
```
|
||||
update-manager -d
|
||||
```
|
||||
|
||||
It may take a couple of minutes before informing you that a new version of Ubuntu is available.
|
||||
|
||||
![Availability of Ubuntu 20.04 in Ubuntu 19.10][11]
|
||||
|
||||
A similar message is displayed in Ubuntu 18.04 as well:
|
||||
|
||||
![Availability of Ubuntu 20.04 in Ubuntu 18.04][12]
|
||||
|
||||
Hit the upgrade button when you see the above message.
|
||||
|
||||
#### Step 4: Start upgrading to Ubuntu 20.04 beta
|
||||
|
||||
The rest of the upgrade procedure is basically waiting for update downloads and clicking okay wherever requested.
|
||||
|
||||
![][13]
|
||||
|
||||
Hit the upgrade button and follow the on-screen instructions.
|
||||
|
||||
![][14]
|
||||
|
||||
You might be notified that all the third party sources have been disabled. At some point, it will also inform you of the packages that will be upgraded, removed etc. It will also ask if you want to keep obsolete packages or not. I prefer to remove them.
|
||||
|
||||
Depending on your internet speed, the upgrade may take a couple of hours. Once the upgrade process is complete, you’ll be asked to restart your system.
|
||||
|
||||
![][15]
|
||||
|
||||
This video shows all the steps in action:
|
||||
|
||||
See, it wasn’t that difficult. Enjoy all the new features in Ubuntu 20.04.
|
||||
|
||||
Questions or suggestions? Feel free to leave a comment below.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://itsfoss.com/upgrade-ubuntu-beta/
|
||||
|
||||
作者：[Abhishek Prakash][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://itsfoss.com/author/abhishek/
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://itsfoss.com/ubuntu-20-04-release-features/
|
||||
[2]: https://www.youtube.com/watch?v=9u5B0njRgOw
|
||||
[3]: https://www.youtube.com/c/itsfoss?sub_confirmation=1
|
||||
[4]: https://itsfoss.com/how-to-know-ubuntu-unity-version/
|
||||
[5]: https://i0.wp.com/itsfoss.com/wp-content/uploads/2020/03/upgrade-ubuntu-20-04-beta.jpg?ssl=1
|
||||
[6]: https://itsfoss.com/ppa-guide/
|
||||
[7]: https://i0.wp.com/itsfoss.com/wp-content/uploads/2020/03/software-updates-app-ubuntu.jpg?ssl=1
|
||||
[8]: https://i1.wp.com/itsfoss.com/wp-content/uploads/2020/03/ubuntu-upgrade-version-settings.jpg?ssl=1
|
||||
[9]: https://itsfoss.com/ubuntu-shortcuts/
|
||||
[10]: https://itsfoss.com/update-ubuntu/
|
||||
[11]: https://i0.wp.com/itsfoss.com/wp-content/uploads/2020/03/upgrade-ubuntu-20-04.jpg?ssl=1
|
||||
[12]: https://i2.wp.com/itsfoss.com/wp-content/uploads/2020/03/upgrade-ubuntu-20-04-from-18-04.jpg?ssl=1
|
||||
[13]: https://i2.wp.com/itsfoss.com/wp-content/uploads/2020/03/upgrade-ubuntu-20-04-steps-1.jpg?ssl=1
|
||||
[14]: https://i0.wp.com/itsfoss.com/wp-content/uploads/2020/03/upgrade-ubuntu-20-04-steps-2.jpg?ssl=1
|
||||
[15]: https://i2.wp.com/itsfoss.com/wp-content/uploads/2020/03/restart-to-finish-beta-upgarde-ubuntu-20-04.jpg?ssl=1
|
||||
@ -1,5 +1,5 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: ( )
|
||||
[#]: translator: (MjSeven)
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: ( )
|
||||
[#]: translator: (geekpi)
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
|
||||
@ -0,0 +1,107 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: ( )
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
[#]: subject: (Meet LBRY, A Blockchain-based Decentralized Alternative to YouTube)
|
||||
[#]: via: (https://itsfoss.com/lbry/)
|
||||
[#]: author: (Abhishek Prakash https://itsfoss.com/author/abhishek/)
|
||||
|
||||
Meet LBRY, A Blockchain-based Decentralized Alternative to YouTube
|
||||
======
|
||||
|
||||
_**LBRY is a new Blockchain-based, open source platform for sharing digital content. It is gaining popularity as a decentralized alternative to YouTube but LBRY is more than just a video sharing service.**_
|
||||
|
||||
### LBRY is an open source blockchain based platform for content sharing
|
||||
|
||||
At the core of it, [LBRY][1] is a new protocol which is a peer to peer, decentralized file sharing and payment network secured by [blockchain][2] technology. Anyone can build apps on top of LBRY protocol that interact with digital content on the LBRY network. But these technical stuff is for developers.
|
||||
|
||||
As a user you can use [LBRY platform][3] for watching videos, listening to music and reading eBooks.
|
||||
|
||||
As a content creator, you can use LBRY to share your digital content like video, music, images, podcasts, eBooks etc.
|
||||
|
||||
Unlike YouTube, your activities are not tracked to serve you ads. In fact, LBRY is ad free. If you are logged into the network, you won’t see any ads anywhere on its website.
|
||||
|
||||
### No ads, and you may even earn cryptocurrency for viewing videos on LBRY
|
||||
|
||||
The LBRY is ‘governed’ by its own cryptocurrency called LBC (LBRY Credits).
|
||||
|
||||
Like any other cryptocurrency, you can mine it, buy it or get it from someone else. Content creators can set a price in LBC for streaming their content or they can provide it for free and get tipped in LBC by the viewers.
|
||||
|
||||
Don’t worry, you don’t necessarily need to buy LBC. Since its new, you’ll get LBC as rewards for doing simple tasks as viewing videos, exploring LBRY, following channels etc. In fact, you’ll get a few LBC simply for creating an account at LBRY and setting up your profile.
|
||||
|
||||
![LBRY Rewards Sample][4]
|
||||
|
||||
You’ll also get LBC in rewards for inviting other users to LBRY platform. For example, if you join [LBRY from It’s FOSS invite link][5], both you and I get LBC as reward.
|
||||
|
||||
The LBRY reward system will change once the platform grows. Remember initially Bitcoins were also readily available and now it values thousands of dollars.
|
||||
|
||||
### Open source, peer to peer, blockchain: LBRY ticks all the right blocks for a privacy-aware user
|
||||
|
||||
![LBRY interface][6]
|
||||
|
||||
While the cyptocurrency is essential to create a fair and open marketplace in LBRY, its main feature is the peer to peer, decentralized network using blockchain. LBRY puts emphasis on treating you as user, not a product.
|
||||
|
||||
Everything built to power LBRY is open source. You can find the entire source code on its GitHub repository.
|
||||
|
||||
[LBRY on GitHub][7]
|
||||
|
||||
The [LBRY FAQ page][8] is a good resource to know more about LBRY and how it works.
|
||||
|
||||
### Using LBRY
|
||||
|
||||
![][9]
|
||||
|
||||
If you want to give LBRY a try, you can check out its [video sharing platform][3]. If you are logged in or using its app, you won’t see any ads.
|
||||
|
||||
Creating an account on LBRY will also let you get the LBRY rewards (i.e. the LBC cryptocurrency). You can watch the videos on LBRY web site or on its application.
|
||||
|
||||
I have noticed that video streaming is slightly faster when you use the app instead of web browser. [LBRY app is available][10] for Linux, Windows, macOS, iOS and Android.
|
||||
|
||||
As a web publisher, It’s FOSS is on all major social media channels. We appreciate and respect such decentralized services and try to make a presence on such offbeat platform. You can [find us on Mastodon][11], a [decentralized alternative to Twitter][12]. You can also find It’s FOSS on LBRY.
|
||||
|
||||
While we will be putting our video content primarily on YouTube and Vimeo (for ad-free experience), our YouTube content will be automatically available on LBRY as well.
|
||||
|
||||
So if you are going to use LBRY, you can follow us there to watch all our videos on LBRY.
|
||||
|
||||
[Join LBRY and follow It’s FOSS][5]
|
||||
|
||||
### Conclusion
|
||||
|
||||
There may not be a lot of content on LBRY right now. LBRY is trying to encourage and reward creators who publish on LBRY first instead of YouTube.
|
||||
|
||||
LBRY is in early stages but its team is working hard to become a viable alternative to YouTube. It has an open road map where they have shared an insight into all their future plans. You may [check it out yourself][13].
|
||||
|
||||
By the way, LBRY is not the only platform of this kind. [PeerTube][14] is a similar service that provides a peer to peer video sharing platform.
|
||||
|
||||
_**If you are someone who doesn’t like tech giants like Google, Microsoft, Huawei ‘spying’ on your data, keeping a profile of you to serve you targeted ads, you may try platforms like PeerTube and LBRY.**_
|
||||
|
||||
What do you think of LBRY? Are you already using something like LBRY or PeerTube? If not, are you willing to give it a try? What’s your overall feeling about P2P platforms like LBRY? Do share your views in the comment section.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://itsfoss.com/lbry/
|
||||
|
||||
作者：[Abhishek Prakash][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://itsfoss.com/author/abhishek/
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://lbry.com/
|
||||
[2]: https://en.wikipedia.org/wiki/Blockchain
|
||||
[3]: https://lbry.tv/
|
||||
[4]: https://i0.wp.com/itsfoss.com/wp-content/uploads/2020/04/lbry-rewards-sample.png?ssl=1
|
||||
[5]: https://lbry.tv/$/invite/@itsfoss:0
|
||||
[6]: https://i0.wp.com/itsfoss.com/wp-content/uploads/2020/04/lbry.png?ssl=1
|
||||
[7]: https://github.com/lbryio/
|
||||
[8]: https://lbry.com/faq
|
||||
[9]: https://i0.wp.com/itsfoss.com/wp-content/uploads/2020/04/lbry-interface.jpg?ssl=1
|
||||
[10]: https://lbry.com/get
|
||||
[11]: https://mastodon.social/@itsfoss
|
||||
[12]: https://itsfoss.com/mastodon-open-source-alternative-twitter/
|
||||
[13]: https://lbry.com/roadmap
|
||||
[14]: https://joinpeertube.org/
|
||||
@ -0,0 +1,164 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: (robsean)
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
[#]: subject: (Use the Fluxbox Linux desktop as your window manager)
|
||||
[#]: via: (https://opensource.com/article/19/12/fluxbox-linux-desktop)
|
||||
[#]: author: (Seth Kenlon https://opensource.com/users/seth)
|
||||
|
||||
使用 Fluxbox Linux desktop 作为你的窗口管理器
|
||||
======
|
||||
这篇文章是Linux 桌面24天的特别系列的一部分。
|
||||
Fluxbox 对系统资源的占用非常轻量，但是它拥有重要的 Linux
|
||||
桌面特色来使你的用户体验轻松快速高效。
|
||||
![在蓝色区域中是，在浏览器上的文本编辑器][1]
|
||||
|
||||
桌面的概念可谓是仁者见仁智者见智。很多人把桌面看作一个家基地，或者一个舒适的客厅，甚至是一个字面意义上的桌面，在其中放置着他们经常使用的记事本，最好的笔和铅笔，还有他们最喜欢的咖啡杯。KDE, GNOME, Pantheon (等等)在 Linux 上提供了这种舒适的生活方式。
|
||||
|
||||
但是对一些用户来说，桌面只是一个空荡荡的监控控件，将还没有自由浮动的应用程序窗口直接投射到显示器上的一个侧面效果。对于这些用户来说，桌面是真空的，在其中他们可以运行应用程序—不管的大型办公软件和图形套件，还是一个简单的终端窗口，或是来管理服务的停靠小程序。这种操作一台 [POSIX][2] 计算机的模式有很长的历史，该家族树的一支是 *box 窗口管理器：Blackbox, Fluxbox 和 Openbox 。
|
||||
|
||||
[Fluxbox][3] 是一个针对 X11 系统的窗口管理器，它基于一个较老的名为 Blackbox 的项目。当我发现 Linux 时，Blackbox 的开发已进入衰退期，因此我进入 Fluxbox ，此后我至少在一个以上的活跃的系统上使用它。它使用 C++ 编写，并在 MIT 开源许可证下授权。
|
||||
|
||||
### 安装 Fluxbox
|
||||
|
||||
你很可能会在你的 Linux 发行版的存储库中找到 Fluxbox ，但是你也可以在 [Fluxbox.org][4] 上找到它。如果你正在运行一个不同的桌面，在同一个系统上安装 Fluxbox 是安全的，因为 Fluxbox 不预先决定任何配置或附带应用程序。
|
||||
|
||||
在安装 Fluxbox 后，注销你当前的桌面会话，以便你可以登录一个新的桌面会话。默认情况下，你的桌面会话管理器 (KDM, GDM, LightDM 或 XDM，取决于你的安装设置) 将你继续登录到上一个在桌面，所以你在登录前必需要覆盖上一个桌面。
|
||||
|
||||
使用 GDM 覆盖一个桌面：
|
||||
|
||||
![在 GDM 中选择你的桌面会话][5]
|
||||
|
||||
或者使用 KDM:
|
||||
|
||||
![使用 KDM 选择你的桌面会话][6]
|
||||
|
||||
### 配置 Fluxbox 桌面
|
||||
|
||||
当你第一次登录到桌面时，屏幕大部分是空的，因为 Fluxbox 提供的所有东西是面板(用于任务栏，系统托盘等等)和用于应用程序窗口的窗口装饰品。
|
||||
|
||||
![在 CentOS 7 上的默认 Fluxbox 配置][7]
|
||||
|
||||
如果你的发行版提供一个简单的 Fluxbox 桌面，你可以使用 **feh** 命令 (你可能需要从你的发行版存储库中来安装它) 来为你的桌面设置背景。这个命令有一些用于设置背景的选项，包括使用你选择的墙纸来填充屏幕的 **\--bg-fill** ，来按比例缩放的 **\--bg-scale** 等等选项。
|
||||
|
||||
|
||||
```
|
||||
`$ feh --bg-fill ~/photo/oamaru/leaf-spiral.jpg`
|
||||
```
|
||||
|
||||
![应用主题的 Fluxbox ][8]
|
||||
|
||||
默认情况下，Fluxbox 自动生成一个菜单，在桌面上任意位置右键单击可用该菜单，这给予你访问应用程序的能力。取决于你的发行版，这个菜单可能非常小，也可能列出 **/usr/share/applications** 目录中的所有启动程序。
|
||||
|
||||
Fluxbox 配置是在文本文件中设置的，这些文本文件包含在 **$HOME/.fluxbox** 目录中。你可以：
|
||||
|
||||
* 在 **keys** 中设置键盘快捷键
|
||||
* 在 **startup** 中启动服务和应用程序
|
||||
* 在 **init** 设置桌面首选项(例如工作区数量、面板位置等等)
|
||||
* 在 **menu** 中设置菜单项
|
||||
|
||||
|
||||
|
||||
该文本配置文件非常易于逆向工程，但是你也可以 (并且是应该) 阅读 Fluxbox [文档][9] 。
|
||||
|
||||
例如，这是我的典型菜单 (或者说至少有它的基本结构)：
|
||||
|
||||
|
||||
```
|
||||
# 为使用你自己的菜单，复制这些文本到 ~/.fluxbox/menu，然后编辑
|
||||
# ~/.fluxbox/init ，并更改 session.menuFile 文件到 ~/.fluxbox/menu
|
||||
|
||||
[begin] (fluxkbox)
|
||||
[submenu] (apps) {}
|
||||
[submenu] (txt) {}
|
||||
[exec] (Emacs 23 (text\)) { x-terminal-emulator -T "Emacs (text)" -e /usr/bin/emacs -nw} <>
|
||||
[exec] (Emacs (X11\)) {/usr/bin/emacs} <>
|
||||
[exec] (LibreOffice) {/usr/bin/libreoffice}
|
||||
[end]
|
||||
[submenu] (code) {}
|
||||
[exec] (qtCreator) {/usr/bin/qtcreator}
|
||||
[exec] (eclipse) {/usr/bin/eclipse}
|
||||
[end]
|
||||
[submenu] (graphics) {}
|
||||
[exec] (ksnapshot) {/usr/bin/ksnapshot}
|
||||
[exec] (gimp) {/usr/bin/gimp}
|
||||
[exec] (blender) {/usr/bin/blender}
|
||||
[end]
|
||||
[submenu] (files) {}
|
||||
[exec] (dolphin) {/usr/bin/dolphin}
|
||||
[exec] (konqueror) { /usr/bin/kfmclient openURL $HOME }
|
||||
[end]
|
||||
[submenu] (network) {}
|
||||
[exec] (firefox) {/usr/bin/firefox}
|
||||
[exec] (konqueror) {/usr/bin/konqueror}
|
||||
[end]
|
||||
[end]
|
||||
## 更改窗口管理器或工作环境
|
||||
[submenu] (environments) {}
|
||||
[restart] (flux) {/usr/bin/startfluxbox}
|
||||
[restart] (ratpoison) {/usr/bin/ratpoison}
|
||||
[exec] (openIndiana) {/home/kenlon/qemu/startSolaris.sh}
|
||||
[end]
|
||||
|
||||
[config] (config)
|
||||
[submenu] (styles) {}
|
||||
[stylesdir] (/usr/share/fluxbox/styles)
|
||||
[stylesdir] (~/.fluxbox/styles)
|
||||
[end]
|
||||
[workspaces] (workspaces)
|
||||
[reconfig] (reconfigure)
|
||||
[restart] (restart)
|
||||
[exit] (exeunt)
|
||||
[end]
|
||||
```
|
||||
|
||||
该菜单也提供一些首选项设置，例如，选择一个主题和从 Fluxbox 会话中重启或注销的能力。
|
||||
|
||||
我使用键盘快捷键来启动大多数的应用程序，这些快捷键写入到 **keys** 配置文件中。这里有一些示例 ( **Mod4** 按键是超级按键，我使用其来指定全局快捷键)：
|
||||
|
||||
|
||||
```
|
||||
# 打开应用程序
|
||||
Mod4 t :Exec konsole
|
||||
Mod4 k :Exec konqueror
|
||||
Mod4 z :Exec fbrun
|
||||
Mod4 e :Exec emacs
|
||||
Mod4 f :Exec firefox
|
||||
Mod4 x :Exec urxvt
|
||||
Mod4 d :Exec dolphin
|
||||
Mod4 q :Exec xscreensaver-command -activate
|
||||
Mod4 3 :Exec ksnapshot
|
||||
```
|
||||
|
||||
在这些快捷方式和一个打开的终端之间，在我工作日的大部分时间内很少使用鼠标，因此从一个控制器切换到另一个控制器不会浪费时间。并且因为 Fluxbox 很好地避开了控制器之间切换的方法，因此在其中操作没有一丝干扰。
|
||||
|
||||
### 为什么你应该使用 Fluxbox
|
||||
|
||||
Fluxbox 对系统资源的占用非常轻量，但是它拥有重要的功能来使你的用户体验轻松快速高效。它很容易定制，并且它允许你定义你自己的工作流。你不必使用 Fluxbox 的面板，因为在这里有其它的极好的面板。你甚至可以鼠标双击和拖动两个独立的应用程序窗口到彼此之中，以便它们成为一个窗口，每个窗口都有自己的选项卡。
|
||||
|
||||
|
||||
无穷的可能性，所以今天就在你的 Linux 上尝试一下 Fluxbox 的简单稳定吧！
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/19/12/fluxbox-linux-desktop
|
||||
|
||||
作者：[Seth Kenlon][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[robsean](https://github.com/robsean)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://opensource.com/users/seth
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/browser_blue_text_editor_web.png?itok=lcf-m6N7 (Text editor on a browser, in blue)
|
||||
[2]: https://opensource.com/article/19/7/what-posix-richard-stallman-explains
|
||||
[3]: http://fluxbox.org
|
||||
[4]: http://fluxbox.org/download/
|
||||
[5]: https://opensource.com/sites/default/files/advent-gdm_0.jpg (Select your desktop session in GDM)
|
||||
[6]: https://opensource.com/sites/default/files/advent-kdm.jpg (Select your desktop session with KDM)
|
||||
[7]: https://opensource.com/sites/default/files/advent-fluxbox-default.jpg (Default Fluxbox configuration on CentOS 7)
|
||||
[8]: https://opensource.com/sites/default/files/advent-fluxbox-green.jpg (Fluxbox with a theme applied)
|
||||
[9]: http://fluxbox.org/features/
|
||||
@ -1,155 +0,0 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: (wxy)
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
[#]: subject: (5 ways to level up your Vim skills)
|
||||
[#]: via: (https://opensource.com/article/20/3/vim-skills)
|
||||
[#]: author: (Detlef Johnson https://opensource.com/users/deckart)
|
||||
|
||||
提升你的 Vim 技能的 5 个方法
|
||||
======
|
||||
|
||||
> 通过一些有趣的技巧使你的文本编辑器更上一层楼。
|
||||
|
||||
![Computer keyboard typing][1]
|
||||
|
||||
Vim 是最受欢迎的文本编辑器之一，因此绝对值得花时间学习如何使用它。如果你使用这个无处不在的 [Vi(m)][2] 命令行文本编辑器来做的只是打开文件、输入和编辑一些文本、保存编辑的文件并退出程序，那么你还有很大的提示空间、。
|
||||
|
||||
在某些情况下你会发现，使用 Vim 非常方便的的场景几乎总是涉及到运行远程 Shell 操作的任务。如果你时不时地使用 ssh，比如
|
||||
|
||||
```
|
||||
$ ssh user@hostname.provider.com
|
||||
```
|
||||
|
||||
并在虚拟专用服务器（VPS）或本地虚拟化容器中工作，那么就可以从这些强大的 Vim 技能中受益匪浅。
|
||||
|
||||
### 将 Vim 设置为默认的文本编辑器
|
||||
|
||||
几乎在所有现代 Linux（或 BSD）发行版中，都可以在终端仿真器的 shell 命令提示符下使用 Vim。在用户 shell 程序中将 Vim 定义为默认编辑器后，即可使用熟悉的 Vim 键绑定来浏览内置的实用程序，例如 `man`。我将说明如何使用 Bash 和 Z shell（zsh）来实现此目的，zsh 现在是 macOS 用户的默认shell（自 Catalina 起）。
|
||||
|
||||
#### 在 Bash 中将 Vim 设置为默认
|
||||
|
||||
Bash 通过点文件的组合来管理设置。将首选编辑器添加到主目录中的 `.bashrc` 文件中是最常见的，但也可以将其添加到 `.bash_profile` 中。（请阅读 [GNU Bash 文档][3]了解不同之处）。
|
||||
|
||||
通过在 `~/.bashrc` 中添加以下内容，将 Vim 设置为默认编辑器：
|
||||
|
||||
```
|
||||
# set default editor to Vim
|
||||
export EDITOR=vim
|
||||
```
|
||||
|
||||
以 `#` 开头的行是可选的注释，这是提醒自己该命令的功能的好方法。
|
||||
|
||||
#### 在 zsh 中将 Vim 设置为默认
|
||||
|
||||
zsh 是一种越来越流行的终端模拟器，尤其是自苹果的基于 FreeBSD 的 Darwin 系统最近从 Bash 切换到 zsh 以来。
|
||||
|
||||
zsh 点文件与 Bash 的文件相当，因此你可以在 `~/.zshrc` 或 `~/.zprofile` 之间进行选择。有关何时使用哪一个的详细信息，请参见 [zsh文档][4]。
|
||||
|
||||
将其设置为默认：
|
||||
|
||||
```
|
||||
# set default editor to Vim
|
||||
export EDITOR=vim
|
||||
```
|
||||
|
||||
### 优化 Vim 配置
|
||||
|
||||
Vim 很像终端仿真器外壳，它使用点文件来设置个人偏好。如果发现该模式，则可能已经猜到它是 `~/.vimrc`。
|
||||
|
||||
你可能要更改的第一个设置是将对旧 Vi 兼容模式切换为“关”。由于 Vim 是 Vi 的超集，因此 Vi 中的所有功能都可用，并在 Vim 中进行了很大的改进，你可以获得许多高级功能。最新版本（8.2）允许你在拆分的窗口中打开终端运行一个子进程 shell 程序。
|
||||
|
||||
顺便说一句，关闭旧版兼容性似乎没有做什么事情（[事实上，可能不是][5]）。当遇到一个 `.vimrc` 文件时，Vim 会自动将该模式切换为关闭。但有时将其明确关闭仍然很重要。缩写 `nocp` 是 `nocompatible` 的同义词，也可以使用它。[条条大道通罗马][6]，切换首选项有很多方式。
|
||||
|
||||
在 `.vimrc` 语法中， 以 `"` 开头的行是注释（就像 `.bashrc` 文件中的 `#` 一样），这些注释可以帮助你记住诸如为何选择一个隐秘的设置名称之类的内容。
|
||||
|
||||
要关闭 Vi 兼容性，请将以下内容添加到 `~/.vimrc` 文件中：
|
||||
|
||||
```
|
||||
" ensure that legacy compatibility mode is off
|
||||
" documentation: <http://vimdoc.sourceforge.net/htmldoc/options.html\#'compatible>'
|
||||
set nocp
|
||||
```
|
||||
|
||||
### 理解模式
|
||||
|
||||
Vim的 “模式”概念是非常重要的，尤其是“正常模式”和“插入模式”之间的区别。对模式的混淆是大多数新用户的困扰。模式并不是 Vim 所独有的，甚至也不是 Vi 所引入的。命令模式是如此的古老，以至于它比 70 年代的[复制和粘贴][7]功能的发明还要早。
|
||||
|
||||
#### 重要的模式
|
||||
|
||||
Vim 依赖于不同的模式来定义键盘的敲击行为。需要了解的重要模式有
|
||||
|
||||
* 正常模式：默认模式，主要用于导航和打开文件。
|
||||
* 插入模式（包括替换）：这种模式下 Vim 允许将文本输入到打开的文件中。
|
||||
* 可视模式：Vim 的行为类似于基于鼠标的输入方式，如复制、编辑、替换等。
|
||||
* 命令模式（包括行模式、Ex 命令模式和末行模式）：在 Vim 中做更多事情的强大方法。
|
||||
|
||||
每种模式都有很多值得探索的地方。使用 [Vimtutor][8]（`vimtutor`）可以交互式地学习移动光标、模式和在末行模式下运行 Ex 命令。一些不可缺少的生产力操作符包括：
|
||||
|
||||
`:E` | 打开资源管理器，用于定位文件和目录。
|
||||
--- | ---
|
||||
`.` | 重复上次的编辑操作。
|
||||
`;` | 向前重复上一次的动作或移动
|
||||
`,` | 向后重复上一次的动作或移动。
|
||||
`/` | 向前搜索文档。
|
||||
`?` | 向后搜索文档。
|
||||
`*` | 查找光标所在处的单词的下一个出现的地方。
|
||||
`#` | 查找光标所在处的单词的上一次出现的地方。
|
||||
`~` | 切换大小写。
|
||||
`%` | 在打开和关闭的 `()`、`[]` 和 `{}` 之间切换；对编码非常有用。
|
||||
`z=` | 提出拼写建议。
|
||||
|
||||
### 像钢琴一样弹奏 Vim
|
||||
|
||||
把 Vim 的操作符“语言”记在记忆中是很重要的，但要想掌握它，难点在于学会像音乐家一样思考，把操作符和动作组合成“和声和弦”，这样你就可以像弹钢琴一样弹奏 Vim。这就是 Vim 的文本操作能力可以与另一个著名的命令行编辑器 Emacs 相媲美的地方。（虽然其中一个编辑器会让磨损掉你的 `Esc` 键，而另一个编辑器会让你的 `Ctrl` 键磨损掉。）
|
||||
|
||||
在描述和弦时，Vim 中的传统做法是用大写字母 `C` 来指代 `Ctrl` 键，后面加上一个连字符（`C-`）。这并不是通用的，但我将从这里开始遵循这一惯例，并在有可能引起混淆的时候加以说明。
|
||||
|
||||
如果你在 Vim 中键入长行，你会想把它设置成可以换行你的文字。想要根据你的工作方式对 Vim 进行个性化设置，请考虑一下这个设置：当 Vim 启动时，你希望 Vim 默认情况下如何处理文本换行？开着还是关着？我喜欢将其关闭，并在运行时用命令打开它。当我想让文本换行时，我只需在命令行模式下用 `:set wrap` 设置即可。
|
||||
|
||||
让 Vim 设置为默认文字换行并没有什么问题。这只是一个偏好的问题 —— 它可能随着时间的推移而改变。同样你也可以控制粘贴、代码语言缩进语法和 `Tab` 键的设置（制表符还是空格？多少个空格？可也在[这里][9]深入研究这些选项）。所有这些默认行为的选项都是完全可配置的，并且在你使用命令行模式操作时可以实时更改。
|
||||
|
||||
你会在社区论坛、Vim 维基和文章中找到很多关于设置 Vim 默认设置的建议（比如这篇文章）。为你的个人计算环境设置首选项对你来说应该相当熟悉，Vim 也不例外。我强烈建议你从对你的设置进行非常小的更改开始，慢慢地进行更多的更改，这样你就可以轻松地恢复设置。这样一来，你就可以避免使用插件好多年或完全不用。
|
||||
|
||||
### Vim 8.2中的分割、标签和终端
|
||||
|
||||
有两种方法可以将你正在处理的文件分割成不同的视图：它们可以并排显示，也可以使用应用程序标签页在全屏（窗口）中切换。这些对应用程序窗口的更改是从命令模式启动的，这需要使用冒号（`:`）来调起提示符。
|
||||
|
||||
每个分割的窗口可以容纳一个文件进行编辑，你可以通过标签页在更多的文件之间随意切换。分割的屏幕空间是有限的，所以当你想分割更多的屏幕时，标签页是很方便的。想要如何设置，纯属个人喜好的问题。要横向分割一个窗口，使用 `:sp`，垂直分割时使用 `:vs`。
|
||||
|
||||
从 [Vim 8.2][10] 开始，你可以用 `:vert term` 打开一个垂直分割的终端 shell 子进程，来在你的代码旁边在命令行进行操作。你需要键入 `exit` 来关闭你的终端进程，就像你结束一个 shell 会话一样，但你关闭这个分割的窗口和标签页的方式和关闭任何普通的 Vim 窗口一样，用 `:q` 来关闭。
|
||||
|
||||
要初始化一个标签页，请使用一个特殊的编辑命令：`:tabedit`，它会自动切换到新打开的标签页。如果你给该命令一个文件名作为参数，将会打开该文件并进行编辑。如果你忽略了给它一个文件名作为参数，可以在命令行模式下的使用编辑命令 `:e filename.txt`，就像在任何一个普通的 Vim 窗口中一样。可以使用下一个（`:tabn`）和上一个（`:tabp`）命令在标签页间导航。
|
||||
|
||||
要使用分割，你需要知道如何使用组合键 `C-w` 和你想要移动的方向的移动键，例如左（`h`）、下（`j`）、左（`k`）、右（`l`）。如果你想学习更多的组合键，请阅读 Vim 手册中的 `:help split` 和 `:help tabpage`。
|
||||
|
||||
### 获取帮助
|
||||
|
||||
虽然可以在 Vimtutor 中打开参考 Vim 手册，但用 `:help` 打开 Vim 帮助，可以让你自己把时间花在编辑器上，不用完全依赖像这样的文章，就能获得更多的成果。经验是掌握 Vim 的关键。经验有助于提高你的整体计算直觉，因为 Vim 中的很多东西都是从 Unix 宇宙中汲取的。
|
||||
|
||||
祝你在探索 Vim 之美的过程中玩得开心，有什么问题可以在评论中分享。
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/20/3/vim-skills
|
||||
|
||||
作者：[Detlef Johnson][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/deckart
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/keyboaord_enter_writing_documentation.jpg?itok=kKrnXc5h (Computer keyboard typing)
|
||||
[2]: https://www.vim.org/
|
||||
[3]: https://www.gnu.org/software/bash/manual/html_node/Bash-Startup-Files.html
|
||||
[4]: http://zsh.sourceforge.net/Intro/intro_3.html
|
||||
[5]: http://vimdoc.sourceforge.net/htmldoc/starting.html#compatible-default
|
||||
[6]: https://en.wikipedia.org/wiki/There%27s_more_than_one_way_to_do_it
|
||||
[7]: https://www.npr.org/2020/02/22/808404858/remembering-the-pioneer-behind-your-computers-cut-copy-and-paste-functions
|
||||
[8]: http://www2.geog.ucl.ac.uk/~plewis/teaching/unix/vimtutor
|
||||
[9]: https://opensource.com/article/18/9/vi-editor-productivity-powerhouse
|
||||
[10]: https://www.vim.org/vim-8.2-released.php
|
||||
@ -0,0 +1,134 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: (HankChow)
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
[#]: subject: (How to Upgrade to Ubuntu 20.04 Beta from 18.04 & 19.10)
|
||||
[#]: via: (https://itsfoss.com/upgrade-ubuntu-beta/)
|
||||
[#]: author: (Abhishek Prakash https://itsfoss.com/author/abhishek/)
|
||||
|
||||
如何将 Ubuntu 18.04/19.10 升级到 Ubuntu 20.04 beta
|
||||
======
|
||||
|
||||
[Ubuntu 20.04 LTS 版本][1]还有不到一个月就发布了，Ubuntu 在这一个版本中对视觉效果作出了大变动，同时在性能方面也有所提高。
|
||||
|
||||
如果你还在使用 Ubuntu 18.04 LTS 版本，你会发现 Ubuntu 20.04 配合深色 Yaru 主题非常惊艳，看过 [Ubuntu 20.04 的展示视频][2]你就知道了。
|
||||
|
||||
[订阅我们的 YouTube 频道观看更多 Linux 视频][3]
|
||||
|
||||
感觉确实不错。如果你想在 4 月 23 日最终稳定版正式发布前率先使用 Ubuntu 20.04，也可以在官方网站上下载 beta 版本。尽管如此，它的稳定性并不差，同时你也可以在使用这个版本的过程中帮助 Ubuntu 团队进行测试。
|
||||
|
||||
你可以下载<ruby>每日构建<rt>daily build</rt></ruby>版并进行重新安装，如果你正在使用的是 Ubuntu 18.04 或 Ubuntu 19.10，也可以在现有系统的基础上直接升级到 Ubuntu 20.04 beta 版本。
|
||||
|
||||
如果你需要确认正在使用的 Ubuntu 版本，可以参考[这篇文章][4]。
|
||||
|
||||
在本文中，我将会介绍如何升级到 Ubuntu 20.04 beta 版本。
|
||||
|
||||
### 如何将 Ubuntu 18.04/19.10 升级到 Ubuntu 20.04 beta
|
||||
|
||||
![Upgrade Ubuntu 20 04 Beta][5]
|
||||
|
||||
在你阅读后面的内容之前，我首先说明一些关于升级到 Ubuntu beta 版本的常见问题。
|
||||
|
||||
* 版本升级的过程并不复杂，但在整个过程中需要有良好的网络连接，以便下载高达好几 GB 的数据。
|
||||
* 版本升级的过程中，第三方存储库（比如你自行添加的 [PPA][6]）会被禁用，有些 PPA 可能也和新版本不兼容，在版本升级完毕后，你可以手动启用 PPA。
|
||||
* 强烈建议将重要数据备份到外部的 USB 硬盘上。你只需要将各个目录下的重要文件直接复制到外部 USB 硬盘上保存即可。
|
||||
* 升级到新版本之后，就无法再回滚到之前的旧版本了，只能重新安装旧版本系统。
|
||||
* 如果你选择升级到 Ubuntu 20.04 beta 版本，那么在 Ubuntu 20.04 最终稳定版发布之后，你也不需要重新安装。只需要保持定期更新 Ubuntu 系统，届时你就可以直接用上最终稳定版了。
|
||||
* Ubuntu 16.04/17/18/19.04 都无法直接升级到 Ubuntu 20.04。
|
||||
|
||||
了解完上面的内容之后，下面开始从 Ubuntu 18.04/19.10 升级到 Ubuntu 20.04。
|
||||
|
||||
#### 步骤 1：检查设置是否正确
|
||||
|
||||
进入“<ruby>软件和升级<rt>Software & Updates</rt></ruby>”应用：
|
||||
|
||||
![Software & Updates application in Ubuntu][7]
|
||||
|
||||
在“<ruby>升级<rt>Updates</rt></ruby>”选项卡中，设置“有任何新版本 Ubuntu 都提醒我”或“有 LTS 版本 Ubuntu 就提醒我”:
|
||||
|
||||
![Ubuntu Upgrade Version Settings][8]
|
||||
|
||||
设置完成后，系统会刷新软件库缓存。
|
||||
|
||||
#### 步骤 2：安装系统更新
|
||||
|
||||
在上面的步骤完成之后，打开终端（在 Ubuntu 中可以使用 `Ctrl+Alt+T` [快捷键][9]），然后使用以下命令[更新 Ubuntu 系统][10]：
|
||||
|
||||
```
|
||||
sudo apt update && sudo apt full-upgrade
|
||||
```
|
||||
|
||||
`apt full-upgrade` 或 `apt dist-upgrade` 的功能和 `apt upgrade` 大致相同，但对于系统版本的升级，`apt full-upgrade` 会在需要的情况下将当前已安装的软件移除掉。
|
||||
|
||||
更新安装完成后，系统可能会需要重新启动。在重新启动之后，就可以进入步骤 3 了。
|
||||
|
||||
#### 步骤 3：使用更新管理器查找开发版本
|
||||
|
||||
在步骤 2 中已经安装了所有必要的更新，现在通过下面的命令打开更新管理器，其中 `-d` 参数表示需要查找开发版本：
|
||||
|
||||
```
|
||||
update-manager -d
|
||||
```
|
||||
|
||||
整个过程可能需要好几分钟，随后会提示有新版本的 Ubuntu 可用：
|
||||
|
||||
![Availability of Ubuntu 20.04 in Ubuntu 19.10][11]
|
||||
|
||||
在 Ubuntu 18.04 上的提示是这样的：
|
||||
|
||||
![Availability of Ubuntu 20.04 in Ubuntu 18.04][12]
|
||||
|
||||
然后点击对话框中的“<ruby>升级<rt>upgrade</rt></ruby>”按钮。
|
||||
|
||||
#### 步骤 4：开始升级到 Ubuntu 20.04 beta
|
||||
|
||||
接下来只要等待下载更新就可以了，遇到对话框直接点击 OK 即可。
|
||||
|
||||
![][13]
|
||||
|
||||
点击“<ruby>升级<rt>upgrade</rt></ruby>”按钮，然后按照提示进行操作。
|
||||
|
||||
![][14]
|
||||
|
||||
在升级过程中，可能会有提示信息告知所有第三方源都已经禁用。有时候还会提示有哪些软件包需要升级或删除，以及是否需要保留一些已经过时了的软件包。一般情况下，我会选择直接删除。
|
||||
|
||||
整个升级过程通常会需要几个小时，但主要还是取决于实际的网速。升级完成后，系统会提示需要重新启动。
|
||||
|
||||
![][15]
|
||||
|
||||
下面的视频展示了所有相关步骤。
|
||||
|
||||
由此可见，这个升级流程并不复杂。欢迎体验 Ubuntu 20.04 带来的新特性。
|
||||
|
||||
如果你有疑问或建议，欢迎在评论区留言。
|
||||
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://itsfoss.com/upgrade-ubuntu-beta/
|
||||
|
||||
作者：[Abhishek Prakash][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[HankChow](https://github.com/HankChow)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://itsfoss.com/author/abhishek/
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://itsfoss.com/ubuntu-20-04-release-features/
|
||||
[2]: https://www.youtube.com/watch?v=9u5B0njRgOw
|
||||
[3]: https://www.youtube.com/c/itsfoss?sub_confirmation=1
|
||||
[4]: https://itsfoss.com/how-to-know-ubuntu-unity-version/
|
||||
[5]: https://i0.wp.com/itsfoss.com/wp-content/uploads/2020/03/upgrade-ubuntu-20-04-beta.jpg?ssl=1
|
||||
[6]: https://itsfoss.com/ppa-guide/
|
||||
[7]: https://i0.wp.com/itsfoss.com/wp-content/uploads/2020/03/software-updates-app-ubuntu.jpg?ssl=1
|
||||
[8]: https://i1.wp.com/itsfoss.com/wp-content/uploads/2020/03/ubuntu-upgrade-version-settings.jpg?ssl=1
|
||||
[9]: https://itsfoss.com/ubuntu-shortcuts/
|
||||
[10]: https://itsfoss.com/update-ubuntu/
|
||||
[11]: https://i0.wp.com/itsfoss.com/wp-content/uploads/2020/03/upgrade-ubuntu-20-04.jpg?ssl=1
|
||||
[12]: https://i2.wp.com/itsfoss.com/wp-content/uploads/2020/03/upgrade-ubuntu-20-04-from-18-04.jpg?ssl=1
|
||||
[13]: https://i2.wp.com/itsfoss.com/wp-content/uploads/2020/03/upgrade-ubuntu-20-04-steps-1.jpg?ssl=1
|
||||
[14]: https://i0.wp.com/itsfoss.com/wp-content/uploads/2020/03/upgrade-ubuntu-20-04-steps-2.jpg?ssl=1
|
||||
[15]: https://i2.wp.com/itsfoss.com/wp-content/uploads/2020/03/restart-to-finish-beta-upgarde-ubuntu-20-04.jpg?ssl=1
|
||||
Loading…
Reference in New Issue
Block a user