ace-window VS melpa

Thanks that is helpful. I do have a question though. Is there any plugin similar to ace-window? I frequently have a situation where I have two frames (basically two windows) that are connected to the same Emacs process, and I am jumping between buffers in both frames.

Looks good. But https://github.com/abo-abo/ace-window was a game-changer for me :-)

take a look at https://github.com/abo-abo/ace-window

I recently started using workspaces in my workflow, and although I know many packages are available in Emacs such as the ones mentioned in the comments, but what worked for me so far is just make a second frame and use ace-window with the variable aw-scope set to 'frame. And from there I just move one frame to the appropriate workspace in my desktop environment and that's it. It's worth keeping in mind that the buffers are still shared so might not be the perfect workspace experience, but I don't think that matters in Emacs.

Try the ace-window package. I think you're referring to C-x o which is bound to other-window.

Also highly recommend ace-window.

I'd like to use ffap (to open files/dirs) in windows I select with ace-window (https://github.com/abo-abo/ace-window). Similar to what aw-switch-buffer-in-window and aw-switch-buffer-other-window do, but with find-file-at-point instead of buffer selection. Crucially, the point means the where I am when the function is called.

If someone has a big monitor I recommend changing C-x 1 delete-other-windowsto revert to have 2 windows open, (like in this config) and using ace-window to navigate to your many windows.

Ace-Window is meant to replace `other-window' by assigning each window a short, unique label

Watch the new pull requests to melpa: https://github.com/melpa/melpa/pulls

(require 'package) (add-to-list 'package-archives '("melpa" . "https://melpa.org/packages/") t) (package-initialize) (package-install 'use-package) (use-package exec-path-from-shell :ensure t :config (exec-path-from-shell-initialize)))

MELPA is definitely the biggest package archive, probably mostly on account of the lower barrier to entry compared to GNU ELPA (maybe the difference would have been less pronounced if NonGNU ELPA had been there from the beginning, but one can only speculate). MELPA has its own requirements for packages, but indeed copyright assignment to the FSF is not one of them.

I would suggest to start at reading the manual first. Then I would recommend reading the Melpa guidance, even if you do not plan to contribute your package to Melpa, since it contains very useful info about linting, writing your code etc.

The mxtoolbox link checks for SMTP blacklisting.. People won't be able to send mail from host with the IP address 178.128.185.1(which is the melpa.org webserver, not their mailserver, so everything's fine there).

Xah asked for his packages to be removed from MELPA a while back: https://github.com/melpa/melpa/issues/7755

Observe that package.el compile files when they are installed, and they are not compiled in any particular order (actually whatever directory-files returns, which is what OS returns). So if you have multiple files that depend on each other, it is something to think of. There are also some guidelines on how to structure your project on Melpa.