the annoying, recurring error message:
Error running timer `doc-view-display’: (error “Selecting deleted buffer”)
what to do:
M-x cancel-timer
Cancel timers of function: doc-view-display
Update 2019-11-05 (GNU Emacs 26.3 on Mojave):
M-x cancel-function-timers
Cancel timers of function: doc-view-display
I first came across MELPA through jira-markup-mode:
Editing Jira markup in a simple browser text pane is a PITA. So I shall give this a try!
kill-ring-save is actually remapped to *table--cell-kill-ring-saveThat “feature” (marking the buffer as changed) is terribly annoying!!! You try to copy (AKA kill-ring-save) text from a table, and from now on something “tells” you, you “changed” the table – but actually you did not. You may be tempted to think, saving a file is a cheap operation, but what if the file is actually located on a remote machine and you are operating on the file through tramp and you cannot reach the machine for a couple of hours?!!
Why not change the buffer to read-only and kill-ring-save than? if you try to kill-ring-save in read-only mode, emacs shouts at you:
apply: Buffer is read-only: #<buffer …>
But yes, although emacs shouted at you, you succeeded copying the text in question to the kill-ring, and now you can paste it into wherever you want.
Rendering an emacs table as HTML table, possible for further intermediate processing – like splitting … – quite useful!
So far I have always printed an emacs table as fixed-font text document – sort of ugly, but still useful.
I find it very useful and necessary to know immediately, that a table got recognised by emacs as such. Emacs shows it in colours then.
With the default settings I find the background blue1 (together with foreground gray90) sometimes / often “far too heavy”, let’s say: a contrast far too exhausting for my eyes. Really!
But what is a “less heavy” pair of foreground / background settings for table-cell? “For the time being” I am using plain “black” for the background through emacs customisation (“table-cell” in my “custom-file“).
The StackExchange article explains you everything, you need to know, and also points you to the related customisation buffer.
| foreground | background | |
| default | black | |
| “light grey” | “dark blue” | |
| 2019-08-27: too difficult | snow1 | gray70 |
| 2019-08-27: works | black | white |
| 2019-08-27: works | tomato | white |
What a surprise! I would have liked to use that functionality for a long, long time – not only in the context of a file under VC. How often did my symlinks get disconnected erroneously / accidentally from their link targets?
Why didn’t I know of such a basic and useful feature for so many years???