Description

Setting org-journal-dir variable in dot-file does not automatically update the auto-mode-list variable when running the emacsclient; it requires a restart of the emacsclient. Please add to the documentation.

(In contrast, setting the value via the customization buffer do

I created this meta issue to track missing documentation. I added [x] even
thought documentation might not be complete. This point is just to make easier
to people to find what module needs documentation, so they can easier contribute
to documentation.

If you want to contribute to documentation there is snippet template,
M-x -> yas-snippet-insert ->Doom module readme
Or in org-mode you ca

It should be possible to edit a commit by visiting one of its blobs, and then editing and saving the blob-visiting buffer.

Upon saving the blob buffer a new commit is created that is identical to the commit the original blob came from, except that it contains the updated blob. If the original commit is reachable from the current branch, then saving also rebases that onto the modified commit.

Next relies on some external programs: keepassxc or pass for the password manager, youtube-dl for the default video downloader, notify-osc (linux) or terminal-notifier (macos) and, well, git for M-x git-clone.

It would be nice if Next suggested to install those if they were missing, at the first call, and do it in the background. Speci

There're 4 possible ways of using :ensure

;; 1
(use-package org
  :ensure t
)

;; 2
(use-package org
  :ensure nil
)

;; 3
(use-package org
)

;; 4
(use-package org
  :ensure org-plus-contrib
)

I understand that t would install the package if absent, while nil would load if present or skip. However, I don't see what the default (i.e. omission of ensure)

Expected behavior

No warnings about unused lexical arguments

Actual behavior

Steps to reproduce the problem

install projectile-2.0.0 from melpa-stable
using use-package. Prior to installing projectile there are zero warnings.
After installing projectile the byte comp

Is the functionality in CIDER compatible with https://github.com/snoe/clojure-lsp ? I figure that would allow all of the CIDER goodies to work across platforms/editors if it was under LSP.

Hello! First of all, thanks for building this! It fulfills a lot of my needs and is a rather uniquely positioned product in that it appears to have no reasonable competitors. I have a lot of data hosted in a Minio instance, and I needed a more user-friendly access layer with indexing, search, and especially thumbnail generation. This seems to do those things well.

#113 gets into these issues

Vscode handles > in tags by calling html/tag and eventually closing the tag.

Example request:

[Trace - 7:58:44 AM] Sending request 'html/tag - (138)'. Params: { "textDocument": { "uri": "file:///home/kyoncho/Sources/lsp-docker/demo-projects/Scala/hello/src/test/scala/example/foo.html" }, "position": { "line": 0, "character": 6 } }

[Trace - 7:58:44 AM] Received response 'html/tag 

Ruby Sass is deprecated. See http://sass.logdown.com/posts/7081811.

As far as I can see, counsel-git-grep currently provides no control over the set of files searched. In a large project I think that one does want this. For example:

1. You know ahead of time that you are looking for something in a certain file or subtree.
2. Faced with many search hits, you want to filter them by source file.

Git itself provides the fairly powerful [pathspec](https://git-sc

Issue type

• Enhancement request

Environment

Emacs version: 26.1
Operating System: Fedora 29 x86_64
Evil version: 1.2.13
Evil installation type: MELPA
Graphical/Terminal: Terminal
Tested in a make emacs session (see CONTRIBUTING.md): Yes

Reproduction steps

• Start Emacs
• Enter some text:

According to docstring M-x sp-clone-sexp RET on (| ()) should yield

(  ())
(  ())

because point is two spaces before an sexp, i.e. not immediately before. But the actual behavior results in

(  ()
   ())

as if it were executed on ( |()).

• smartparens version: 20190103.2309
• Active major-mode: lisp-interaction-mode
• Smartparens strict mode: t
• Emacs

When calling a function in REPL, SLIME shows the lambda-list of the function at the bottom of the screen. The currently expected argument(the one that cursor is at) is bold.

However, this behaviour can be broken by using #P. When #P reader macro is used, it is treated as an argument itself.

Test case(ignore that the call is invalid):
(format #P"test")

Expected behaviour:
After movin

From a discussion with @trefis, I don't think that merlin shows the documentation for record fields like it does for normal values. It would be nice if it did.

In the Issue #161 we have been talking about the org-brain "API", and the need to document the use of the org-brain functions from elisp with the needed arguments, parameters, etc. I want to work with you in what you need related to the more complex linking workflow possible.

All about the issue #163 is a good example of a coding, reference and documentation need for me. How do I

This file structure:

$ ls
mycode.c  other_file.c
$ git init
Initialized empty Git repository in /home/gauthier/tmp/dumb/.git/
$ git add mycode.c && git commit -m"Init"
[master (root-commit) 5271e5a] Init
 1 file changed, 15 insertions(+)
 create mode 100644 mycode.c

mycode.c:

typedef int my_type_t;

my_type_t a;
my_type_t my_function(my_type_t in);
int main(void)

Issue #409 introduced a new function to indicate which systems support symlinks:

(defun straight--windows-os-p ()
  "Check if the current operating system is Windows."
  (memq system-type '(ms-dos windows-nt cygwin)))

cygwin should not be in this list, it supports symlinks. It runs on windows-os, but in its own environment, with its own filesystem including /tmp, /proc, .. and its ow

I often end up creating multiple configurations, that basically does the same thing. It would be nice if the commands supported variable references to such things as current buffer/file. This could allow for more use-cases and generic configurations.

This is currently supported by Visual Studio code, see https://code.visualstudio.com/docs/editor/variables-reference

I think it is a kind of ne

It seems like the / is causing unintentional italics. I don't know org formatting rules, but maybe it needs to be escaped? If not, maybe the formatting engine is off?