The Project Explorer and Outline views in Eclipse have a Link with Editor feature that can be very useful. This can be enabled in either view, by clicking the down arrow button in the view and choosing Link with Editor (see screenshot above).
If Link with Editor is enabled in Project Explorer: The current file open in the Editor will be highlighted in Project Explorer.
If Link with Editor is enabled in Outline: The class or method at the location of the cursor will be highlighted in Outline.
sudoedit is the recommended command to use to edit files owned by the superuser. On many systems, it uses the nano editor to open these files. You might prefer to use a different editor like Vim to edit these files.
The man page for sudoedit says that the editor used is decided based on the environment variables EDITOR, SUDO_EDITOR or VISUAL. Setting these variables proved to be useless, since it did not affect the editor used by sudoedit.
The method that works is to run sudo update-alternatives --config editor and choose your preferred editor from the list that is displayed. It works and sudoedit starts using the editor you picked.
Eclipse has support for version control systems like Git, SVN and CVS. Support for Mercurial can be enabled by using the MercurialEclipse plugin. When viewing files in version control, it is common practice to quickly see which of the lines are uncommitted compared to the current head (or parent) revision. This information can be viewed in Eclipse by using its Quick Diff feature. This is easy to do:
Go to Window -> Preferences -> General -> Editors -> Text Editors -> Quick Diff. This is the dialog from where it can be configured.
Turn on Quick Diff, by enabling the option Enable quick diff.
Choose the version control system for which Quick Diff is needed from the dropdown Use this reference source. Git, SVN and CVS should be present here. Mercurial appears if the MercurialEclipse plugin is installed.
The overview ruler is the ruler to the right of the scrollbar in the editor. If you would like to see the uncommitted lines to be marked on it, enable the option Show differences in overview ruler.
Choose Apply and OK. Close all editor windows and reopen the source file that you want in the editor.
You should be able to see the newly added, modified or deleted lines marked in colors in the left bar on which line numbers are usually displayed. The colors used are the ones set in the Quick Diff dialog (see above steps). You can also view these uncommitted locations marked along the overview ruler on the right.
Small and simple XML files can be viewed and edited using Vim. However, a XML viewer and editor is required if the XML file is large and complicated. XML Copy Editor is a viewer and editor for XML files that runs on Ubuntu.
To install it:
$ sudo apt install xmlcopyeditor
Tried with: XML Copy Editor 18.104.22.168 and Ubuntu 14.04
Markdown has become an essential file format, especially if you are sharing source code on Github or Bitbucket. ReText is a good Markdown editor for Ubuntu. It can be installed easily:
$ sudo apt install retext
I like to use ReText in the live preview mode where the resulting HTML is shown in a pane on the right. So, it acts as an excellent Markdown viewer too. I have no idea why this is not turned on by default.
The markdown format is increasingly used at websites like GitHub. Thus, there is a need for a simple markdown editor that can be used to edit and view markdown files.
MarkdownPad is a markdown editor for Windows which I found does this job well. Just download and install. Associate .md files with MarkdownPad, which can be found as MarkdownPad.appref-ms in the directory %USERPROFILE%\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\MarkdownPad
Tried with: MarkdownPad 22.214.171.124 and Windows 7 Professional x64
I was using Texmaker as my LaTeX editor on Windows until recently. It was sufficient as an editor, but I was not fully happy with its autocompletion and multi-file UI. I came across TeXstudio, which is a fork of Texmaker and it turns out it fills out all the features I felt were missing in Texmaker and it seems to be more updated. For example, the autocompletion of LaTeX commands, references and citations actually works. Also, if you have structured your document as multiple LaTeX files, compiling from any of them compiles the document. If you are a Texmaker user, do try out TeXstudio.