Assuming that you are referring to plain text…
while keeping them as clickable links
First of all you need to establish why a plain text URL is doing something when you click on it, as your new requirement is going to need to interact with that.
(I’m guessing goto-address-mode is enabled, so I would check that first.)
C-x a in Magit’s menusM-x remove-hook has alleviated that to an extent.Use named functions. It’s just better.
Check C-h v comint-process-echoes in that buffer.
If it’s nil, try (setq-local comint-process-echoes t)
If that fixes it, then you can use this repl’s major mode hook to do that automatically.
Have you considered an org-capture template fitting your desired format?
I don’t use use-package, but I’ve seen a lot of questions from users who do use it but don’t understand how to use it, or what it’s going to expand to, or what the things that it expands to actually do. My conclusion has been that for some users it introduces as many problems as it solves. I think those users would be better off if they learned how to manage their config without it first, and only considered use-package after understanding the more fundamental building blocks upon which it is built.
It’s certainly not something you need to use, in any case. It’s clearly an invaluable system to many users, but if you don’t get along with it, don’t use it.
Awesome; thank you.
The author of the emacs pgtk code says that no one who has X installed should use pgtk – he’s stated on several occasions that if you have X at all then you should use a supported X toolkit in Emacs for best results.
I’ve seen counter-arguments that pgtk is still beneficial if you happen to have a “high DPI display”, but I believe that’s the only argument I’ve ever seen for using pgtk under X.
I always build --with-x-toolkit=lucid myself, and can happily vouch for that one. I don’t use Wayland, though.
Looks like a bug (whether documentation or code) as read-kbd-macro still claims to return a string if possible, but nowadays it forcibly returns a vector. Please M-x report-emacs-bug to get that clarified.
You could extract a string of characters from the vector:
(mapconcat (lambda (event)
(and (characterp event)
(char-to-string event)))
(read-kbd-macro "C-c"))
But if you look at the code for read-kbd-macro you’ll see that it calls this:
(defun edmacro-parse-keys (string &optional _need-vector)
(let ((result (kbd string)))
(if (stringp result)
(seq-into result 'vector)
result)))
Hence the string value you wanted is coming from kbd:
(kbd "C-c") => "^C"
There are of course arguments you can pass to kbd which won’t return a string, but that would always have been the case for your code, and presumably you’re not attempting to use any of those.
A couple of simple config suggestions:
(winner-mode 1) ;; Get familiar with `winner-undo'.
(global-set-key (kbd "C-x !") 'delete-other-windows-vertically)
I get a lot of mileage out of those two.
Also consider adding bindings for these, to tell the following command where to display its buffer:
And the regular windmove commands are very convenient for moving between buffers.
The transpose-frame package available in MELPA is useful. Note that with only two windows, rotate-frame is “exchange the positions of the windows”, and transpose-frame is “switch between vertical and horizontal split”. I have those bound to C-c | and C-c \ respectively, and use them regularly.
You don’t have to declare a new variable each time you want to remember an old value. You could, e.g., put a custom symbol property on the variable symbol with the old value (or list of old values) you wanted to store. Or maintain a single variable mapping all your variable symbols to their old values.
Ok. Mine doesn’t, but I’ll believe yours does. Why is that making it hard to for you to share it between machines?
the configuration contains a lot of junk
What do you mean? What is the specific problem?
I don’t know, but the initial denote release for Emacs was barely 16 months ago, so it would be fairly surprising if anyone had written support for another editor so quickly.
Maybe if you define a minimum set of features which would be adequate for collaboration purposes, you could ask in vim forums how you might go about implementing those.
You’re matching the literal text :init|config|custom
Tip: Use M-x re-builder to test.
C-h f message to add to the *Messages* buffer (C-h e to jump to that).
If Emacs will start a long-running process and react whenever there’s new output, then you’ll want to see C-h i g (elisp)Asynchronous Processes and C-h i g (elisp)Output from Processes. (n.b. I’ve added a couple of other notes to my initial reply, too.)
Tell us how you run that external program outside of Emacs, and we can show you how to run it inside Emacs.
Then it’s just a matter of timers and a variable in your mode-line-format. Note that your variable will need the risky-local-variable in order to show text properties (for the colour). See C-h i g (elisp)Mode Line Data and/or C-h i g (elisp)Properties in Mode.
If you ensure that everything that you want to be compiled is currently compiled, you can let https://github.com/emacscollective/auto-compile manage it from there.