mirror of
https://github.com/LCTT/TranslateProject.git
synced 2024-12-26 21:30:55 +08:00
zxp
GitHub
commit
ca820371fb
@ -1,67 +0,0 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: (geekpi)
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
[#]: subject: (Why Java developers love the jEdit text editor)
|
||||
[#]: via: (https://opensource.com/article/20/12/jedit)
|
||||
[#]: author: (Seth Kenlon https://opensource.com/users/seth)
|
||||
|
||||
Why Java developers love the jEdit text editor
|
||||
======
|
||||
This editor packs the power of Java and offers plenty of plugins to
|
||||
streamline your workflow.
|
||||
![Person drinking a hot drink at the computer][1]
|
||||
|
||||
Java is a powerful language. Maybe because it’s often seen as an "industrial-strength" tool, you might not expect it to be the foundation of a text editor. After all, text editing is almost too easy for such power. In fact, in most modern programming toolkits, the component accepting text entry is a pre-programmed widget. Using a Java toolkit, a simple text editor can be written in about 100 lines of code. So what can [jEdit][2] possibly offer to justify its existence?
|
||||
|
||||
Well, quite a lot, actually! The jEdit application is a refreshing reminder of just how practical and useful Java can be for even everyday desktop apps. It deftly demonstrates the dynamism of its foundational technology, and ever true to Java’s enduring promise, it does so on _all_ platforms.
|
||||
|
||||
### Installing jEdit
|
||||
|
||||
jEdit is written in Java, so it’s available for any platform. [Download it][3] in a generic installer or in a custom installer for the OS of choice. Once it’s downloaded (it’s small, so it won’t take long), run the installer.
|
||||
|
||||
If you don’t have Java installed, learn how to install Java on [Linux][4], [Mac, or Windows][5].
|
||||
|
||||
### Using jEdit
|
||||
|
||||
The way you edit text in jEdit is the same as editing text in any desktop text editor. If you’ve used one, you’ve basically used jEdit; all the common keyboard shortcuts and conventions apply. There are also some features commonly aimed at coders—line numbering, folding (in which sections of text are hidden so you can focus on other sections), and syntax highlighting.
|
||||
|
||||
But imagine, for a moment, text editors on a spectrum from [Vim simplicity][6] to [Emacs complexity][7], and you’ll find jEdit happily making its home alongside Emacs. While the editing component is typical of any desktop editing app, jEdit’s additional features include plugins, macros that you can record live during your editing session, features specific to certain editing modes, buffer options, and more. This is an editor that actively encourages you to make it your own.
|
||||
|
||||
There are three places you can go for jEdit customization: buffer options, global options, and the plugins manager.
|
||||
|
||||
Buffer options (in the Utilities menu) allow you to adjust settings associated with your current document. Usually, jEdit auto-detects the appropriate mode to use for what you’re doing. For instance, writing XML triggers jEdit’s XML highlighting. Sometimes, though, you want to override what jEdit has detected or failed to detect. You can also turn on Explicit Folding mode, which allows you to manually define sections of text you want jEdit to treat as foldable sections.
|
||||
|
||||
Global options (in the Utilities menu) offer dozens of preferences that get treated as jEdit’s defaults. This can include anything from its appearance to custom shortcuts.
|
||||
|
||||
Plugins extend jEdit in ways its developers, literally, never intended. Plugins offer ways of working that just aren’t "normal" for jEdit, but that just might transform a laborious task into something easy or even fun. It practically transformed XML workflow with its excellent XML parsing, its _Outline_ plugin available for its dockable _Sidekick_ panel, and XSLT integration. If I were not already using Netbeans for Java code, I can imagine using jEdit instead.
|
||||
|
||||
### jEdit for programmers
|
||||
|
||||
Which text editor you choose depends on what you intend to do in your editor. This one calls itself the "programmer’s text editor," and I feel it’s a very strong contender for serious Java and XML work. However, it doesn’t have quite the same feature set when editing Lua code and Bash scripts. Compared to something like Emacs, for instance, jEdit’s code folding is less flexible (I couldn’t get it to fold a Lua function without additional markup). While it does have a rich plugin selection, I was unable to find anything particularly persuasive for work in AsciiDoc and other non-code formats.
|
||||
|
||||
The most appealing feature of jEdit, for me, is its foundation in Java. Because it runs in a JVM, you can be confident that you can use it regardless of your platform and possibly regardless of whether you have permission to install applications outside your own home directory. Java is a popular and active language, so jEdit’s features and plugins are well-maintained.
|
||||
|
||||
You should try jEdit if you’re a fan of consistency, or a Java developer, or just an XML geek trying desperately to get out of oXygen. It’s easy to get started, and it’s a lot of fun to explore.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/20/12/jedit
|
||||
|
||||
作者：[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/coffee_tea_laptop_computer_work_desk.png?itok=D5yMx_Dr (Person drinking a hot drink at the computer)
|
||||
[2]: http://jedit.org
|
||||
[3]: http://www.jedit.org/index.php?page=download
|
||||
[4]: https://opensource.com/article/19/11/install-java-linux
|
||||
[5]: http://adoptopenjdk.org
|
||||
[6]: https://opensource.com/article/20/12/vi-text-editor
|
||||
[7]: https://opensource.com/article/20/12/emacs
|
||||
@ -1,5 +1,5 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: ( )
|
||||
[#]: translator: (geekpi)
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
|
||||
@ -0,0 +1,107 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: ( )
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
[#]: subject: (Explore the exciting features of the Howl text editor)
|
||||
[#]: via: (https://opensource.com/article/20/12/howl)
|
||||
[#]: author: (Seth Kenlon https://opensource.com/users/seth)
|
||||
|
||||
Explore the exciting features of the Howl text editor
|
||||
======
|
||||
Howl is a general-purpose text editor with a super-efficient workflow
|
||||
and plenty of features to keep it fun and interesting.
|
||||
![Typewriter in the grass][1]
|
||||
|
||||
Howl is a general-purpose text editor written in Moonscript and Lua. It’s not focused on a specific programming language, and instead features support for many different languages and formats. In fact, it takes inspiration from "traditional" Unix editors like [Emacs][2] and [Vim][3], so it feels familiar to anyone accustomed to that style of editing. It’s primarily a text-oriented interface, without dialogue boxes, toolbars, or a menu, and yet, it has many exciting features that make it feel a little like an IDE for authors, regardless of whether you write code or prose.
|
||||
|
||||
![Howl][4]
|
||||
|
||||
### Install
|
||||
|
||||
Howl is developed on Linux and for Linux. However, it’s written in Lua with some GTK wrapping, both of which are cross-platform, so if you’re keen to compile code, you can test Howl on Windows or macOS.
|
||||
|
||||
The compile process is relatively simple, provided you have LuaJIT and GTK development libraries installed. In this sample command, `X.Y` represents a version number in tag form:
|
||||
|
||||
|
||||
```
|
||||
$ git clone --depth 1
|
||||
–branch X.Y
|
||||
<https://github.com/howl-editor/howl.git>
|
||||
$ cd howl-X.Y/src
|
||||
$ make
|
||||
$ make install
|
||||
```
|
||||
|
||||
You can launch Howl from your application menu or from a terminal.
|
||||
|
||||
### Using Howl
|
||||
|
||||
Howl is a lightweight editor. It has a fast startup time and a small overall footprint. This is, in part, thanks to LuaJIT, a just-in-time (JIT) compiler for the [Lua programming language][5].
|
||||
|
||||
When you first launch it, the Howl interface is a single empty window. The Howl window contains one view by default, but it can contain more. For instance, you can press **Alt+X** to bring up a command-line view in your Howl window.
|
||||
|
||||
![Black Howl command line box with cursor][6]
|
||||
|
||||
The command line lets you enter editor commands. You use it a lot because Howl has no menu bar and no toolbar. Conveniently, you can press **Tab** for suggested command completion as you type, so it’s actually much faster than a traditional menu for locating a function, even when you don’t know the exact name of the function you’re looking for.
|
||||
|
||||
To dismiss the command-line view, press **Esc** on your keyboard.
|
||||
|
||||
### Opening a file
|
||||
|
||||
To open a file in Howl, press **Alt+X** to bring up a command line and then type `open` followed by a **Space**. Howl displays a new temporary view: a view into your file system so you can choose a file to open. You can choose a file by either typing its path or by clicking on the file you want.
|
||||
|
||||
### Editing text with Howl
|
||||
|
||||
Howl’s interface is optimized for its primary function: to edit text. It makes composing words, whether in code or in a natural language, sublimely efficient. As you type, regardless of what you’re typing, Howl offers predictive completion of the current word. To complete a word as it’s being suggested, press **Return** or **Enter** on your keyboard.
|
||||
|
||||
Everything that happens in the Howl editor view is a function. For instance, when you select a word and press **Ctrl+C** to copy it, you are invoking the `editor-copy` function, which is assigned the **Ctrl+C** key binding. You might be surprised at how many functions are available. For instance, you can copy an entire line of text with the `editor-copy-line` function by typing **Alt+X** to bring up the command-line view and then `editor-copy-line`. If you hadn’t already just read about it here, you might have discovered the function on your own the same way I did: open a command-line view, type a keyword, such as "copy," and press **Tab** for relevant suggestions.
|
||||
|
||||
When you discover functions through the command-line view, you’re also provided with the function’s default keyboard shortcut, if there is one.
|
||||
|
||||
![Black Howl terminal box with white, gray and pink code][7]
|
||||
|
||||
### Saving a file
|
||||
|
||||
After you’re done writing or programming (or both), you probably want to save your work. You can do that, as you might guess, with the `save` function. Open a command-line view with **Alt+X** and then type `save`, or just press **Ctrl+S** on your keyboard.
|
||||
|
||||
### Quit
|
||||
|
||||
Howl is such a great editor, you probably won’t want to quit. However, sometimes you want to experience the joy of opening Howl to see how quickly it loads, and in order to do that, you have to exit. To exit the application, open a command-line view with **Alt+X** and then type `quit`.
|
||||
|
||||
### Extensions and configuration
|
||||
|
||||
Howl doesn’t have an extension language because it’s written in Moonscript and Lua, using the same API available for everyone else. Said another way: Howl is its own extension. Should you find the Howl API insufficient, you can code directly in C by using LuaJIT’s [FFI library][8].
|
||||
|
||||
You can configure Howl in a file called `~/.howl/init.moon` (for Moonscript) or `~/.howl/init.lua` (for Lua).
|
||||
|
||||
Configurable options in Howl are displayed as configuration variables. You can set these variables interactively from within Howl using the `set` command, or you can define them in your Howl init file. To discover new configuration variables, type the `set` command into Howl’s command line, and then press the **Spacebar** to see potential completions.
|
||||
|
||||
If you’re not familiar with Lua, check out my [Lua cheat sheet][9]. Moonscript is arguably even easier if you’re not familiar with Lua yet.
|
||||
|
||||
### Use this editor
|
||||
|
||||
Howl is a pleasure to use and exciting to explore. It’s a lean, focused, and efficient editor with lots of features and an extensible design. If you’re a fan of text, text editing, Lua, or just plain good application design, start using Howl. You won’t `quit` any time soon (but not because you don’t know how).
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/20/12/howl
|
||||
|
||||
作者：[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/doc-dish-lead.png?itok=h3fCkVmU (Typewriter in the grass)
|
||||
[2]: https://opensource.com/article/20/2/who-cares-about-emacs
|
||||
[3]: https://opensource.com/article/20/3/vim-skills
|
||||
[4]: https://opensource.com/sites/default/files/31-howl.jpg (Howl)
|
||||
[5]: https://opensource.com/article/20/2/lua-cheat-sheet
|
||||
[6]: https://opensource.com/sites/default/files/uploads/howl-command-31-howl-opensource.jpg (Black Howl command line box with cursor)
|
||||
[7]: https://opensource.com/sites/default/files/uploads/howl-tab-31-howl-opensource.jpg (Black Howl terminal box with white, gray and pink code)
|
||||
[8]: https://luajit.org/ext_ffi.html
|
||||
[9]: http://opensource.com/article/20/2/lua-cheat-sheet
|
||||
@ -0,0 +1,13 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: ( )
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
[#]: subject: (How to hack Android Auto to display custom content)
|
||||
[#]: via: (https://opensource.com/article/20/12/android-auto-open-source)
|
||||
[#]: author: (Tomasz Grobelny https://opensource.com/users/grobelny)
|
||||
|
||||
How to hack Android Auto to display custom content
|
||||
======
|
||||
Reimplement the Android Auto protocol to cast movies and additional
|
||||
applications on automotive head unit displays.
|
||||
@ -0,0 +1,122 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: ( )
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
[#]: subject: (How to Install RPM Files on Fedora Linux [Beginner’s Tutorial])
|
||||
[#]: via: (https://itsfoss.com/install-rpm-files-fedora/)
|
||||
[#]: author: (Abhishek Prakash https://itsfoss.com/author/abhishek/)
|
||||
|
||||
How to Install RPM Files on Fedora Linux [Beginner’s Tutorial]
|
||||
======
|
||||
|
||||
_**This beginner article explains how to install RPM packages on Fedora and Red Hat Linux. It also shows you how to remove those RPM packages afterwards.**_
|
||||
|
||||
When you start using Fedora Linux in the Red Hat domain, sooner or later, you’ll come across .rpm files. Like .exe files in Windows and .deb files in Ubuntu and Debian, .rpm files enable you to quickly install a software from it on [Fedora][1].
|
||||
|
||||
You could find and install plenty of software from the software center, specially [if you enable additional repositories in Fedora][2]. But sometimes you’ll find software available on their website in RPM format.
|
||||
|
||||
Like .exe files in Windows, you **download the .rpm file and double click on it to install it**. Don’t worry, I’ll show you the detailed steps.
|
||||
|
||||
### Installing RPM files on Fedora and Red Hat Linux
|
||||
|
||||
I’ll be showing you three ways to install RPM files:
|
||||
|
||||
* [Install RPM files with software center][3] (GUI method)
|
||||
* [Install RPM files using DNF command][4] (CLI method)
|
||||
* [Install RPM files using Yum command][5] (CLI method for Red Hat)
|
||||
|
||||
|
||||
|
||||
#### Method 1: Use software center
|
||||
|
||||
The simplest method is to use the default software center in Fedora. It’s really simple. Go to the folder where you downloaded the .rpm file. It is usually the Downloads folder.
|
||||
|
||||
Just **double click on the RPM file and it will be opened in the software center**.
|
||||
|
||||
Alternatively, you can right click on the file and choose to install it via Software Center.
|
||||
|
||||
![Either double click or right click and choose Software Install][6]
|
||||
|
||||
When it is opened in the software center, you should see the installation option. Just hit the install button and enter your account’s password when prompted for it.
|
||||
|
||||
![Install RPM via Fedora Software Center][7]
|
||||
|
||||
It’s easy, right?
|
||||
|
||||
#### Method 2: Use DNF command to install RPM file
|
||||
|
||||
This is the command line method. Fedora uses the new DNF [package manager][8] and you can use it to install downloaded RPM files as well.
|
||||
|
||||
Open a terminal and switch to the directory where you have the RPM file downloaded. You can also provide the path to the RPM file. Use the DNF command like this:
|
||||
|
||||
```
|
||||
sudo dnf install rpm_file_name
|
||||
```
|
||||
|
||||
Here’s a screenshot where I installed [Google Chrome on Fedora with dnf command][9]:
|
||||
|
||||
![Installing RPM files using DNF command][10]
|
||||
|
||||
#### Method 3: Install RPM files in Red Hat using Yum command
|
||||
|
||||
Unlike Fedora, Red Hat still uses the good old Yum package manager. You won’t find the DNF command here, yet.
|
||||
|
||||
The process is the same as DNF command. You go to the directory where the RPM file is located or provide its path.
|
||||
|
||||
```
|
||||
sudo yum install path_to_RPM_file
|
||||
```
|
||||
|
||||
That’s it. Nothing fancier.
|
||||
|
||||
### How to remove RPM packages
|
||||
|
||||
Removing a RPM package isn’t a big deal either. And no, you don’t need the original rpm file that you used to install the program.
|
||||
|
||||
You may find the installed package in the software center and remove application from there.
|
||||
|
||||
![Removing RPM Package][11]
|
||||
|
||||
Alternatively, you can use the DNF or YUM command with `remove` option.
|
||||
|
||||
With DNF, use this command:
|
||||
|
||||
```
|
||||
sudo dnf remove rpm_package_name
|
||||
```
|
||||
|
||||
With Yum, use this command:
|
||||
|
||||
```
|
||||
sudo yum remove rpm_package_name
|
||||
```
|
||||
|
||||
You probably won’t remember the exact package name and that’s fine. What you can do is to type the first few letters of the package and then hit tab. This is assuming that you have tab completion enabled which usually is.
|
||||
|
||||
And that’s all you need to do here. Pretty simple, right? Being a beginner, you may struggle with a simple task like this and I hope you feel more confident with Fedora thanks to quick tutorials like this.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://itsfoss.com/install-rpm-files-fedora/
|
||||
|
||||
作者：[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://getfedora.org/
|
||||
[2]: https://itsfoss.com/fedora-third-party-repos/
|
||||
[3]: tmp.TvkJtlRJ6T#gui-method
|
||||
[4]: tmp.TvkJtlRJ6T#use-dnf
|
||||
[5]: tmp.TvkJtlRJ6T#use-yum
|
||||
[6]: https://i0.wp.com/itsfoss.com/wp-content/uploads/2020/12/installing-rpm-file-fedora.png?resize=800%2C449&ssl=1
|
||||
[7]: https://i1.wp.com/itsfoss.com/wp-content/uploads/2020/12/install-rpm-fedora-software-center.jpg?resize=799%2C193&ssl=1
|
||||
[8]: https://itsfoss.com/package-manager/
|
||||
[9]: https://itsfoss.com/install-google-chrome-fedora/
|
||||
[10]: https://i1.wp.com/itsfoss.com/wp-content/uploads/2020/12/install-rpm-using-dnf-install.jpg?resize=800%2C474&ssl=1
|
||||
[11]: https://i0.wp.com/itsfoss.com/wp-content/uploads/2020/12/remove-rpm-package-fedora.jpg?resize=790%2C190&ssl=1
|
||||
@ -0,0 +1,66 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: (geekpi)
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
[#]: subject: (Why Java developers love the jEdit text editor)
|
||||
[#]: via: (https://opensource.com/article/20/12/jedit)
|
||||
[#]: author: (Seth Kenlon https://opensource.com/users/seth)
|
||||
|
||||
为什么 Java 开发者喜欢 jEdit 文本编辑器
|
||||
======
|
||||
这款编辑器打包了 Java 的功能，并提供了大量的插件来简化你的工作流程。
|
||||
![Person drinking a hot drink at the computer][1]
|
||||
|
||||
Java 是一门强大的语言。也许因为它经常被看作是一种“工业级”的工具，你可能不会想到它会成为文本编辑器的基础。毕竟，对于如此能力，文本编辑几乎是太容易了。事实上，在大多数现代编程工具包中，接受文本输入的组件是一个预编程的小部件。使用 Java 工具箱，一个简单的文本编辑器可以在 100 行左右的代码中编写出来。那么 [jEdit][2] 能提供什么来证明它的存在呢？
|
||||
|
||||
嗯，实际上，它有很多功能！jEdit 应用是一个令人耳目一新的提醒，提醒人们 Java 对于日常桌面应用是多么的实用和有用。它巧妙地展示了它的基础技术的活力，并且永远忠于 Java 的持久承诺，在_所有_的平台上都能使用。
|
||||
|
||||
### 安装 jEdit
|
||||
|
||||
jEdit 是用 Java 编写的，所以它适用于任何平台。[下载][3]通用安装程序或为所选的操作系统下载自定义安装程序。下载完成后（它很小，因此不会花费很长时间），请运行安装程序。
|
||||
|
||||
如果你没有安装 Java，请学习如何在 [Linux][4]、[Mac 或 Windows][5] 上安装 Java。
|
||||
|
||||
### 使用 jEdit
|
||||
|
||||
在 jEdit 中编辑文本的方式和在任何桌面文本编辑器中编辑文本的方式是一样的。如果你使用过一个编辑器，那么你基本上已经使用了 jEdit。所有常用的键盘快捷键和惯例都适用。也有一些通常针对编码者的功能，如行号、折叠（文本的部分被隐藏，这样你就可以把注意力放在其他部分）和语法高亮。
|
||||
|
||||
但是，想象一下，从 [Vim 的简单性][6]到 [Emacs 的复杂性][7]的文本编辑器，你会发现 jEdit 与 Emacs 类似。虽然编辑组件和任何典型桌面编辑应用一样，但 jEdit 的附加功能包括插件、可以在编辑会话中实时录制的宏、特定编辑模式的功能、缓冲区选项等。这是一个积极鼓励你把它变成你自己的编辑器。
|
||||
|
||||
你可以在三个地方对 jEdit 进行自定义：缓冲区选项、全局选项和插件管理器。
|
||||
|
||||
缓冲区选项（在 “Utilities” 菜单中）使你可以调整与当前文档关联的设置。通常，jEdit 会自动检测用于你正在执行的操作的适当模式。例如，编写 XML 会触发 jEdit 的 XML 高亮显示。但是，有时你想覆盖 jEdit 已检测到或未能检测到的内容。你还可以打开“显式折叠”模式，该模式允许你手动定义希望 jEdit 视为可折叠部分的文本。
|
||||
|
||||
全局选项（在 “Utilities” 菜单中）提供了数十种首选项，这些首选项被视为 jEdit 的默认值。这包括从外观到自定义快捷方式的所有内容。
|
||||
|
||||
插件扩展了 jEdit 的功能，实际上，它的开发者从未想过要这样。插件提供的工作方式对 jEdit 而言并非“正常”，但可能会将繁琐的任务转变为简单甚至有趣的事情。它以其出色的 XML 解析、可停靠 _Sidekick_ 面板中的 _Outline_ 插件和 XSLT 集成，实际上改变了 XML 工作流程。如果我还没有使用 Netbeans 来编写 Java 代码，我可以想象使用 jEdit 来代替。
|
||||
|
||||
### 面向程序员的 jEdit
|
||||
|
||||
选择哪种文本编辑器取决于你打算在编辑器中做的事。它称自己为“程序员的文本编辑器”，并且我认为它是认真的 Java 和 XML 工作的有力竞争者。但是，在编辑 Lua 代码和 Bash 脚本时，它的功能不尽相同。例如，与 Emacs 之类相比，jEdit 的代码折叠不那么灵活（我无法在没有附加标记的情况下折叠 Lua 函数）。尽管确实有丰富的插件选择，但我找不到能在 AsciiDoc 和其他非代码格式下工作的特别有说服力的东西。
|
||||
|
||||
对我来说，jEdit 最吸引人的特点是它是以 Java 为基础。因为它在 JVM 中运行，所以你可以有信心可以使用它，而无论你使用的平台是什么，也可以不管你是否有权限在自己的主目录之外安装应用。Java 是一种流行且活跃的语言，因此 jEdit 的功能和插件维护得很好。
|
||||
|
||||
如果你是一贯的忠实拥护者、Java 开发人员，或者只是 XML 极客而拼命试图摆脱 oXygen，那么你应该试试 jEdit。它很容易上手，并且探索起来很有趣。
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/20/12/jedit
|
||||
|
||||
作者：[Seth Kenlon][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[geekpi](https://github.com/geekpi)
|
||||
校对：[校对者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/coffee_tea_laptop_computer_work_desk.png?itok=D5yMx_Dr (Person drinking a hot drink at the computer)
|
||||
[2]: http://jedit.org
|
||||
[3]: http://www.jedit.org/index.php?page=download
|
||||
[4]: https://opensource.com/article/19/11/install-java-linux
|
||||
[5]: http://adoptopenjdk.org
|
||||
[6]: https://opensource.com/article/20/12/vi-text-editor
|
||||
[7]: https://opensource.com/article/20/12/emacs
|
||||
Loading…
Reference in New Issue
Block a user