unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: help-gnu-emacs@gnu.org
Subject: Re: Dired: how to mark with other character but *
Date: Sun, 31 Jan 2021 22:30:03 +0100	[thread overview]
Message-ID: <87h7mwn6as.fsf@web.de> (raw)
In-Reply-To: courier.0000000060164B9D.00007B5F@stw1.rcdrun.com

Jean Louis <bugs@gnu.support> writes:

> I would like to use this specific workflow in Dired like following:
> [...]

As far as I know there is nothing built-in that matches exactly what you
are looking for.

Using different marker chars can be very useful, but it's not that
convenient.  Personally, I have implemented a "secondary" mark.  What I
sometimes miss is the ability to use multiple marks per file.

Anyway, maybe you would like something like this:

#+begin_src emacs-lisp
(defun my-dired-with-marker-prefix-command (char)
  "Prefix command temporarily changing marker char."
  (interactive "cMarker char for next command: ")
  (let ((old-dired-marker-char dired-marker-char)
        (used-once nil))
    (setq dired-marker-char char)
    (letrec ((f (lambda ()
                  (if (not used-once)
                      (setq used-once t)
                    (setq dired-marker-char old-dired-marker-char)
                    (remove-hook 'post-command-hook f 'local)))))
      (add-hook 'post-command-hook f nil 'local))))
#+end_src

A different approach is use stored sets of marked files.  Again, there
is no built-in solution for this (apart from the neglected "virtual
dired" maybe).  AFAIR, dired+ supports this, maybe also other packages.

It's also relatively simple to setup registers for that purpose.


Regards,

Michael.




  parent reply	other threads:[~2021-01-31 21:30 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-31  6:18 Dired: how to mark with other character but * Jean Louis
2021-01-31  6:23 ` Jean Louis
2021-01-31  6:43   ` moasenwood--- via Users list for the GNU Emacs text editor
2021-01-31  7:29     ` Jean Louis
2021-01-31  6:53 ` Marcin Borkowski
2021-01-31  7:23   ` moasenwood--- via Users list for the GNU Emacs text editor
2021-01-31  7:36     ` Jean Louis
2021-01-31  7:46       ` moasenwood--- via Users list for the GNU Emacs text editor
2021-02-01 16:35     ` [External] : " Drew Adams
2021-02-01 17:09       ` Drew Adams
2021-02-01 17:24         ` Drew Adams
2021-02-02  4:15           ` moasenwood--- via Users list for the GNU Emacs text editor
2021-02-05 20:59             ` Drew Adams
2021-02-05 21:02               ` Stefan Monnier
2021-02-05 21:10                 ` Drew Adams
2021-02-01 23:47         ` Drew Adams
2021-02-02  4:14         ` moasenwood--- via Users list for the GNU Emacs text editor
2021-01-31  7:34   ` Jean Louis
2021-01-31  8:20     ` Marcin Borkowski
2021-01-31  9:09       ` Jean Louis
2021-01-31  9:26         ` moasenwood--- via Users list for the GNU Emacs text editor
2021-01-31  9:34           ` moasenwood--- via Users list for the GNU Emacs text editor
2021-01-31 14:47 ` Eli Zaretskii
2021-02-01  2:25   ` Jean Louis
2021-01-31 21:30 ` Michael Heerdegen [this message]
2021-01-31 21:37   ` moasenwood--- via Users list for the GNU Emacs text editor

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87h7mwn6as.fsf@web.de \
    --to=michael_heerdegen@web.de \
    --cc=help-gnu-emacs@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).