take a look at terminator.Ĭouple other quick notes. If you are interested in a more feature rich terminal that does things like split windows, etc.
So unless you have a specific application or question regarding terminal performance I suggest removing xterm from synaptic or removing the menu entries if they are causing confusion and just use lxterminal for LXDE. (So this is not a debate place for terminals - roxterm,xterm,uxterm,urxvt,terminator,tilda, etc) You are using the bash shell regardless of terminal choice - So unless you are programming or have other specific needs the average user uses whats included as the default. The average desktop user does not do much in the terminal except use it when a GUI does not meet their needs for what they are trying to accomplish.
I will look into that for R9 and I am not sure about changing the code specific to the terminal as its a utility.Īs far as what terminal works best for your environment? Thats a debate that could go on forever. The cleanup that probably would be easiest is to simply remove the menu entries for both xterm and uxterm and remove said confusion. If you go look at the package in synaptic (xterm) you will see it says as much in the description, and when xterm is installed, uxterm is as well. Its a wrapper around xterm to provide locale and UTF-8. uxterm is not a separate package (even though it has its own binay). (and I have not changed that code) I considered removing and changing the code before releasing R8, but it was left as is as it added negligible space and overhead and the effort and time made it an easy decision.ģ. xterm is required as the installer uses it and its coded to do as such.
LXterminal comes with LXDE as part of the desktop environment so its included in the install and its a servicable terminal and functions well within LXDE. This site includes much text from previous work by Henrik Levkowetz, Robert Sparks, Russ Housley, Ben Kaduk, Murray Kucherawy, Alvaro Retana, the RFC Production Center, and the members of many IESGs.1. Likewise, the templates and schemas available on this site are published on GitHub and we welcome pull requests proposing changes.
The repository README provides guidance on how to submit pull requests. The content for this site is available in GitHub and we welcome pull requests proposing changes from the community. To find out more about authoring an I-D, begin with Getting started. The term "author" is used here, but the information applies to people acting in any role. Internet-Drafts are prepared by people acting in possibly several roles, such as an author or an editor. Unless otherwise indicated, the information on this site applies to all streams. When an I-D is approved to become an RFC, it follows the separate RFC Editor RFC publication process. For the IETF that is documented in the standards development process. Each of the RFC Streams has their own process for how an I-D becomes an RFC. Some I-Ds may eventually be published as a Request for Comment (RFC). Anyone can write and submit an Internet-Draft. Internet-Drafts (I-Ds) are the basic work items of the IETF and they are produced for a variety of purposes by a wide range of individuals and groups.
The features available at that site have been replaced as follows: If you have been redirected here from then that site has been decommissioned. If you are new to authoring then begin with the introduction below or if you are more familiar then the main menu lists multiple individual topics. This site is the central resource site for authors of an Internet-Draft (I-D), with information on how to write an I-D and the tools available to support this. ¶ Welcome to the Internet-Draft authors resource site