The filtering system is designed after ibuffer: every dired
buffer has associated "filter stack" where user can push
filters (predicates). These filters are by default
logically "anded", meaning, only the files satsifying all the
predicates are shown.

Some filters take additional input from the user such as part of
name, regexp or extension, other filters only use a predefined
predicate such as "show only directories" or "omit dot files".

In addition, there are two "metafilters", the or' filter and the not' filter. These take other filters as arguments and change
their logical interpretation. The or' filter takes the two filters on top of the stack, pops them and pushes a filter that matches files satisfying one or the other (or both) filters. The not' filter pops the top filter and pushes its logical negation.

To enable or disable the filters toggle minor mode
`dired-filter-mode'. Toggling this mode preserves the filter
stack, so you can use it to quickly hide/unhide files filtered by
the current filter setup.

All the provided interactive functions are available from
dired-filter-map'. You can customizedired-filter-prefix' to set
a prefix for this map or bind it manually to a prefix of your
choice using:

(define-key dired-mode-map (kbd "some-key") dired-filter-map)

The bindings follow a convention where the filters are mapped on
lower-case letters or punctuation, operators are mapped on symbols
(such as !, |, * etc.) and group commands are mapped on upper-case
letters. The exception to this is p' which is bound to dired-filter-pop', which is a very common operation and warrants a
quick binding.

In addition to filtering, you can also use the same predicates to
only mark files without removing the rest. All the filtering
functions of the form dired-filter-by-*' have their marking counterpartdired-filter-mark-by-*'. These are available from
dired-filter-mark-map'. You can customize dired-filter-mark-prefix' a prefix for this map or bind it
manually to a prefix of your choice using:

(define-key dired-mode-map (kbd "some-key") dired-filter-mark-map)

The marking operations are not placed on stack, instead, the marks
are immediately updated by "OR"-ing them together. To remove marks
that would otherwise be selected by a filter, use prefix argument
(usually bound to C-u'). To logically negate the meaning of the filter, you can call the function with a double prefix argument (usuallyC-u' `C-u')

You can use saved filters to mark files by calling
`dired-filter-mark-by-saved-filters'.

Forge allows you to work with Git forges, such as Github and Gitlab, from the comfort of Magit and the rest of Emacs.

Forge fetches issues, pull-requests and other data using the forge’s API and stores that in a local database. Additionally it fetches the pull-request references using Git. Forge implements various features that use this data but the database and pull-request refs can also be used by third-party packages.

ρEmacs is a preconfigured distribution of GNU Emacs editor for Microsoft Windows. It offers nearly GNU/Linux Emacs experience in Windows with minimum configuration efforts. A set of additional GNU command-line and development tools is available through the network installer.

(flycheck-define-checker perl-project-libs
  "A perl syntax checker."
  :command ("perl"
            "-MProject::Libs lib_dirs => [qw(local/lib/perl5)]"
            "-wc"
            source-inplace)
  :error-patterns ((error line-start
                          (minimal-match (message))
                          " at " (file-name) " line " line
                          (or "." (and ", " (zero-or-more not-newline)))
                          line-end))
  :modes (cperl-mode))

(add-hook 'cperl-mode-hook
          (lambda ()
            (flycheck-mode t)
            (setq flycheck-checker 'perl-project-libs)))

'(flycheck-perl-include-path
(quote
("your path to your perl libraries")))
'(flycheck-perl-executable "path to your perl executable")

Feature

The doom-modeline was designed for minimalism, and offers:

• A match count panel (for anzu, iedit, multiple-cursors, symbol-overlay,
  evil-search and evil-substitute)
• An indicator for recording a macro
• Current environment version (e.g. python, ruby, go, etc.) in the major-mode
• A customizable mode-line height (see doom-modeline-height)
• A minor modes segment which is compatible with minions
• An error/warning count segment for flymake/flycheck
• A workspace number segment for eyebrowse
• A perspective name segment for persp-mode
• A window number segment for ace-window, winum and window-numbering
• An indicator for evil state
• An indicator for god state
• An indicator for ryo-modal state
• An indicator for xah-fly-keys state
• An indicator for remote host
• An indicator for debug state
• An indicator for current input method
• An indicator for LSP state with lsp-mode or eglot
• An indicator for github notifications
• An indicator for unread emails with mu4e-alert
• An indicator for irc notifications with circe
• An indicator for buffer position which is compatible with nyan-mode
• An indicator for party parrot
• An indicator for PDF page number
• An indicator for battery status with fancy-battery
• Truncated file name, file icon, buffer state and project name in buffer
  information segment, which is compatible with projectile and project

Screenshots

Use magit-ediff or 'e' on an unmerged item to resolve merge conflicts with ediff. Magit will set up an ediff with three buffers A, B and C. A and B are the original (conflicting) files, and C is the conflicted merge.

These notes summarize some of my discoveries (re-)learning GNU Emacs. Since these are my personal notes, it may help to briefly describe my background. I used Emacs on Unix from somewhere around 1990 until 1995. Then in 1995 I began using Windows as my primary operating system and stopped using Emacs. In 2010 I decided to give Emacs on Windows another try. I may not mention some basic things just because I remember them from my initial experience.

Try query-replace enter [ space ] enter M-j enter ! enter