Professional Documents
Culture Documents
Emacs X Window System
Emacs X Window System
If the above method doesn’t work for you or you want to manually compile
emacs, follow these steps:
STEP 1: Download the latest version (26.1) of source code from the gnu
server with following command:
curl https://ftp.gnu.org/pub/gnu/emacs/emacs-26.1.tar.gz
/emacs/emacs-26.1.tar.gz
STEP 2: Extract the tar.gz file.
tar -zxvf emacs-26.1.tar.gz
STEP 3: Install Prerequisites.
sudo apt-get update
sudo apt-get install build-essential libgnutls28-dev libncurses-
dev
STEP 4: Install Emacs.
cd /emacs/emacs-26.1/
./configure #Configure Emacs
make #build components using makefile
sudo make install #Install Emacs
The above steps will install Emacs into your system. To confirm the install,
you can check using terminal using the following command:
emacs --version
Example:
emacs new.txt
Explanation: This command creates a file called new.txt if it doesn’t already
exist.
If the file with that name already exists, it’s content is copied to the memory
buffer and shown at the editing buffer area.
Used primarily on Unix variants, X versions are also available for other
operating systems.
Features of the X window system include network transparency, the
ability to link to different networks, and customizable graphical
capabilities.
X Window System
The client/server model in X system works in reverse to typical
client/server model, where the client runs on the local machine and asks
for services from the server.
In X system, the server runs on the local machine and provides its
display and services to the client programs. The client programs may be
local or remotely exist over different networks, but appear transparently.
Architecture
Limitations
The lack of design guidelines in X has resulted in several vastly different
interfaces, and in applications that have not always worked well together.
The Inter-Client Communication Conventions Manual (ICCCM), a
specification for client interoperability, has a reputation for being difficult
to implement correctly. Further standards efforts such
as Motif and CDE did not alleviate problems. This has frustrated users and
programmers.[5] Graphics programmers now generally address
consistency of application look and feel and communication by coding to a
specific desktop environment or to a specific widget toolkit, which also
avoids having to deal directly with the ICCCM.
X also lacks native support for user-defined stored procedures on the X
server, in the manner of NeWS – there is no Turing-complete scripting
facility. Various desktop environments may thus offer their own (usually
mutually incompatible) facilities.
Systems built upon X may have accessibility issues that make utilization
of a computer difficult for disabled users, including right click, double
click, middle click, mouse-over, and focus stealing. Some X11 clients deal
with accessibility issues better than others, so persons with accessibility
problems are not locked out of using X11. However, there is no
accessibility standard or accessibility guidelines for X11. Within the X11
standards process there is no working group on accessibility, however,
accessibility needs are being addressed by software projects to provide
these features on top of X.