Brief summary of what the package does

A minor mode to keep repositories in sync using the rsync command line tool.

Direct link to the package repository

https://github.com/r-zip/rsync-mode

Your association with the package

I am the primary author. The only other contributor is ajwhite445. @ajwhite445

Relevant communications with the upstream package maintainer

None needed.

Checklist

<!-- Please confirm with x: -->

• [x] The package is released under a GPL-Compatible Free Software License
• [x] I've read CONTRIBUTING.org
• [x] I've used the latest version of package-lint to check for packaging issues, and addressed its feedback
• [x] My elisp byte-compiles cleanly
• [x] M-x checkdoc is happy with my docstrings
• [x] I've built and installed the package using the instructions in CONTRIBUTING.org
• [ ] I have confirmed some of these without doing them

<!-- After submitting, please fix any problems the CI reports. -->

Thanks @jehelset , I will try your code. I really like the concept of separate "reconfigure" command.

Brief summary of what the package does

A fork of pippel, a package to manage python pip on Emacs.

Direct link to the package repository

https://github.com/arifer612/pippel

Your association with the package

New maintainer of the package.

Relevant communications with the upstream package maintainer

https://github.com/brotzeit/pippel/pull/16#discussion_r653597929

Checklist

<!-- Please confirm with x: -->

• [x] The package is released under a GPL-Compatible Free Software License
• [x] I've read CONTRIBUTING.org
• [x] I've used the latest version of package-lint to check for packaging issues, and addressed its feedback
• [x] My elisp byte-compiles cleanly
• [x] M-x checkdoc is happy with my docstrings
• [x] I've built and installed the package using the instructions in CONTRIBUTING.org
• [ ] I have confirmed some of these without doing them

<!-- After submitting, please fix any problems the CI reports. -->

as a quickfix you could use something like this:

(defun projectile-reconfigure-command (compile-dir)
  "Retrieve the configure command for COMPILE-DIR without considering history.

The command is determined like this:

- first we check for `projectile-project-configure-cmd' supplied
via .dir-locals.el

- finally we check for the default configure command for a
project of that type"
  (or projectile-project-configure-cmd
      (let ((cmd-format-string (projectile-default-configure-command (projectile-project-type))))
        (when cmd-format-string
          (format cmd-format-string (projectile-project-root) compile-dir)))))

(defun projectile-reconfigure-project (arg)
  "Run project configure command without considering command history.

Normally you'll be prompted for a compilation command, unless
variable `compilation-read-command'.  You can force the prompt
with a prefix ARG."
  (interactive "P")
  (let ((command (projectile-reconfigure-command (projectile-compilation-dir))))
    (projectile--run-project-cmd command projectile-configure-cmd-map
                                 :show-prompt arg
                                 :prompt-prefix "Configure command: "
                                 :save-buffers t)))

and bind projectile-reconfigure-command to a suitable key.

i think this is simply how the project-type-agnosticprojectile-configure-command works (https://github.com/bbatsov/projectile/blob/master/projectile.el#L4337). it will prefer to use the cached command. to get the behaviour you want, one would have to be able to disable caching of configuration commands. not sure if this is possible currently.

Brief summary of what the package does

A fork of pippel, a package to manage python pip on Emacs.

Direct link to the package repository

https://github.com/arifer612/pippel

Your association with the package

New maintainer of the package.

Relevant communications with the upstream package maintainer

https://github.com/brotzeit/pippel/pull/16#discussion_r653597929

Checklist

<!-- Please confirm with x: -->

• [x] The package is released under a GPL-Compatible Free Software License
• [x] I've read CONTRIBUTING.org
• [x] I've used the latest version of package-lint to check for packaging issues, and addressed its feedback
• [x] My elisp byte-compiles cleanly
• [x] M-x checkdoc is happy with my docstrings
• [x] I've built and installed the package using the instructions in CONTRIBUTING.org
• [ ] I have confirmed some of these without doing them

<!-- After submitting, please fix any problems the CI reports. -->

Brief summary of what the package does

ox-yaow (yaow=yet another org wiki) is designed to be a lightweight as-is org -> html export option. More detailed information can be found in the README below.

Direct link to the package repository

https://github.com/LaurenceWarne/ox-yaow.el

Your association with the package

Maintainer

Relevant communications with the upstream package maintainer

None Needed

Checklist

<!-- Please confirm with x: -->

• [x] The package is released under a GPL-Compatible Free Software License
• [x] I've read CONTRIBUTING.org
• [x] I've used the latest version of package-lint to check for packaging issues, and addressed its feedback
• [x] My elisp byte-compiles cleanly
• [x] M-x checkdoc is happy with my docstrings
• [x] I've built and installed the package using the instructions in CONTRIBUTING.org
• [ ] I have confirmed some of these without doing them

<!-- After submitting, please fix any problems the CI reports. -->

BBDB has some support for storing (base64-encoded) images in the image-uri field. It'd be nice if we could fallback to these when gravatar shows up empty, it'd be something like

(create-image (base64-decode-string
            (bbdb-record-xfield (car (bbdb-search (bbdb-records)
                                                    :mail author-email))
                                'image-uri))
            nil
            'data)

plus error handling

If you are using the default use-package settings they are not equal.

(use-package company-lsp :commands company-lsp) does not require the package since :commands makes it lazy load when that command is invoked.

The corresponding basic plain Emacs LISP expression would be:

(unless
    (fboundp 'company-lsp)
  (autoload #'company-lsp "company-lsp" nil t))

(use-package company-lsp) already requires the company-lsp feature so the additional (require ...) does nothing.

@ztlevi thanks it worked for me.

I want to know if the following two settings are equivalent.

(use-package company-lsp :commands company-lsp)

and

(use-package company-lsp)
(require 'company-lsp)

Regards, HY

Thanks!

I have applied this to the crm branch to avoid having to keep rebasing two branches until I finally get around to finishing this up.

(To be applied to the crm branch.)

In magit-completing-read-multiple*, this avoids changing the return value of split-string. With this, selectrum's crm function works correctly instead of signaling an error.

(The first commit doesn't change behaviour, only formatting, to make the second commit easier.)

Nice, that did it! And I now see that it is documented in the user manual 🤦 . I would be in favor of making this option the default behavior. Other than that, feel free to close this issue.

Brief summary of what the package does

electric-paren enables instant execution of complete expressions in interactive Lisp modes, a feature copied from the Symbolics Genera operating system. I.e., when you press the closing ')' in ielm, eshell, interactive-lisp, sly, or slime it executes immediately, without pressing <return>.

Direct link to the package repository

https://github.com/chrchr/electric-paren

Your association with the package

I am the creator

Relevant communications with the upstream package maintainer

Checklist

<!-- Please confirm with x: -->

• [x ] The package is released under a GPL-Compatible Free Software License
• [x ] I've read CONTRIBUTING.org
• [x ] I've used the latest version of package-lint to check for packaging issues, and addressed its feedback
• [x ] My elisp byte-compiles cleanly
• [x ] M-x checkdoc is happy with my docstrings
• [x ] I've built and installed the package using the instructions in CONTRIBUTING.org
• [ ] I have confirmed some of these without doing them

<!-- After submitting, please fix any problems the CI reports. -->

I need to look at this a bit more. I'll resubmit later. Thank you!

Also see #4394.

================================================================= Use a dedicated feature branch

Please use a dedicated feature branch for your feature request, instead of asking us to merge "your-fork/master" into the "origin/master". The use of dedicated branches makes it much more convenient to deal with pull-requests, especially when using Magit to do so.

If you were about to open a pull-request asking us to merge your version of "master", then see 1 for instructions on how to quickly fix that and some information on why we ask you to do so.

Additionally we ask you to allow us to push to the branch you want us to merge. We might want to push additional commits and/or make minor changes. Please make sure the box next to "Allow edits from maintainers" is checked before creating the pull-request.

================================================================= Do NOT use Github to edit files and create commit messages

Unless you are aware of all the pitfalls and take great care to avoid them, the use of Github results in many small defects, including but not limited to trailing whitespace, commit messages containing overlong lines and no newline at the very end, and "GitHub [email protected]" being used as the committer. The last one cannot even be avoided, which I consider as an affront.

Github is an insufficient interface for editing files and creating commits. Please don't do it when contributing to Magit.

================================================================= What you should write here

git diff -R

================================================================= How to update the manual

If you make changes to the manual, then edit only "magit.org". Do not manually edit "magit.texi". The latter has to be generated from the former. If you want to do that yourself, then follow the instructions at 2. Otherwise a maintainer will do it and amend that to your commit.