In addition to what abo-abo suggests, you can also build the sources by yourself:
git clone git://git.savannah.gnu.org/emacs.git
sudo apt-get build-dep emacs24 # for rpm-based linux: sudo yum-builddep emacs
./configure # if there's no configure script: ./autogen.sh
make # if that fails: make bootstrap
If you provide the universal argument to replace-string, that is by pressing C-u before M-x replace-string, it only replaces matches that are surrounded by word boundaries.
So, for example, a buffer containing
would be become after C-u M-x replace-string RET mod RET off_mod
You can find this information by looking in the ...
This is a great question!
I've found the directions online to install it by hand unclear and, frankly, a bit of a pain (at least on Debian).
Emacs on Debian doesn't come with the Emacs Lisp Reference Manual by default. It's kind of silly, but Debian stores it in the non-free repos. Unfortunately, a regular apt-get install doesn't Just Work™...
No, there isn't, if you don't want to silence your background processes.
You could use something like tmux or GNU Screen for your background processes.
Or you could run them in another terminal.
But Emacs has no way of knowing that some other process is outputting characters to the terminal, as far as I know.
In emacs, Ctl-L will refresh the screen, removing any extra stuff written by your background process.
If the background process only emits stuff every once in a while, then you can just refresh each time.
In general, a terminal application like emacs -nw has only very limited information about what colors are available. The shell will have an environment variable called TERM which contains the name of the terminal you're using. The application can then use a library such as terminfo to pick the right escape sequences to use each feature of the terminal. This ...
It looks like Ubuntu is using it's own numbering system, 45.0ubuntu1 vs 24.4. This may be tricking dpkg into thinking that the Ubuntu version (which appears to be 24.3) is actually newer than your compiled 24.4.
Debian (and thus Ubuntu) provides emacs in a number of different packages, to allow users to stick to a particular version, track the latest release,...
I'm pretty sure that the answer is: try another font.
There was quite a lot of discussion about this problem recently in the thread for bug #20628 of the Emacs bug list.
You will even see some info about particular fonts there, which might be helpful for your particular question. Oh, and note that there were some changes made to how Emacs picks a font, as ...
Make sure that your $TERM is set correctly before running Emacs.
If launching direct from the terminal, check with echo $TERM - preferably its value would be xterm-256color
Set it either directly before you run Emacs:
TERM=xterm-256color emacs -nw
With any other arguments you need.
As a more permanent solution, set the value of TERM in your terminal ...
The fg job control command should work if you run from the same terminal where you entered Control-z.
To find out what processes are available to be placed in the fore ground use the jobs command. If jobs does not list your Emacs process, you're in the wrong shell.
I recommend you first dpkg --remove xemacs21 (and maybe also for related packages like xemacs21-support, xemacs21-mule, xemacs21-nomule, xemacs21-bin, ...), after which the update should work again. Once that is done, you can try to re-install XEmacs (tho, of course, I'd recommend you switch to Emacs instead).
For those who want to run stable emacs 25.1 on Ubuntu 16.10, I pulled the source package from zenity-proposed and pushed it to my ppa for yakkety, so you can install as follows:
sudo add-apt-repository ppa:aperomsik/aap-ppa
sudo apt-get update
sudo apt-get install emacs25
All files under /usr should be world-readable. They're system files that cam be obtained by anyone over the Internet, so there'd be no point in preventing local users from reading them. (There may be exceptions for proprietary software, but even so it is very uncommon to have non-world-readable files under /usr.)
The fact that /usr/share/emacs/25.2/lisp is ...
Assuming that ctrl-c ctrl-x is bound to execute-interpret, then the system should prompt you with the command to run, suggesting as a default /path/to the/script/test.sh as a default. Edit this default value to put single quotes around the whole thing.
A different way would be to change the command to be run to ./test.sh. I suspect that when you say But ...
#+BEGIN_SRC plantuml :file my_file.jpg
gives you a jpg file
#+BEGIN_SRC plantuml :file my_file.png
gives you a png file
#+BEGIN_SRC plantuml :file my_file.txt
gives you a txt file
#+BEGIN_SRC plantuml :file my_file.svg
gives you a svg file
The images are produced by imagemagick
1. Download https://www.gnu.org/software/emacs/manual/info/elisp.info.gz to your /usr/share/info directory.
2. From a terminal run update-info-dir command.
3. From emacs C-h i m Elisp (capital E).
The command /usr/bin/ssh -o ControlPath=%C 0.0.0.1 is used to check, whether your local ssh command accepts the ControlPath option. 0.0.0.1 is a non-existing address; ssh shall return immediately with an error.
In more recent Tramp versions, the blocking is avoided by using the command ssh -o ConnectTimeout=1 -o ControlPath=%C 0.0.0.1. I recommend to upgrade ...
The directory where you put multi-term.el needs to be in your load path. Add this to your .emacs before the 'require' call:
(add-to-list 'load-path "/home/test/.emacs.d")
This should fix your problem, but as @phil points out, it's bad practice to store lisp code in your .emacs.d directory, and it may cause unexpected problems later on. You should ...
I had the same issue. After looking at the source code I figured out it is expecting a file name as a parameter. This code should work:
#+BEGIN_SRC plantuml :file plantuml.svg
(*) --> "First Activity"
-->[You can put also labels] "Second Activity"
For sake of completeness. A look at
ESS on GitHub or
required me to download:
and to install them via:
dpkg -i ess_17.11-4_all.deb elpa-ess_17.11-4_all.deb
Works for me on 18.04.
Edit: The CRAN repository has been updated ...
There are several possible ways that Emacs/TLS can be misconfigured but it seems likely this is simply a duplicate of the question you linked, especially given your distribution's GnuTLS version matching the version I am testing with. My answer is likely to be the cause.
Here's the workaround that I mentioned:
(defun db48x/shell-quote-arg-list (args)
(mapcar 'shell-quote-argument args))
(advice-add 'executable-interpret :filter-args 'db48x/shell-quote-arg-list '(name escape-command-name))
This tells emacs to run the db48x/shell-quote-arg-list function on the argument list any time anyone calls executable-interpret. This ...