unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Tino Calancha <tino.calancha@gmail.com>
To: Emacs developers <emacs-devel@gnu.org>
Subject: Re: 26.0.50; Extend dired-do-shell-command substitutions
Date: Sat, 01 Jul 2017 14:06:01 +0900	[thread overview]
Message-ID: <87k23srbk6.fsf@calancha-pc> (raw)
In-Reply-To: <87r2y6sqsn.fsf@calancha-pc> (Tino Calancha's message of "Tue, 27 Jun 2017 00:38:00 +0900")

Tino Calancha <tino.calancha@gmail.com> writes:

One thing i am not sure is that in my patch i delete
the two variables `dired-star-subst-regexp' and
`dired-quark-subst-regexp': they are just used in dired-aux.el
for the substitutions in `dired-do-shell-command':
> commit cd9877d16edec71e7ea9b1eedd4194d67c1b092e
> Author: Tino Calancha <tino.calancha@gmail.com>
> Date:   Tue Jun 27 00:18:45 2017 +0900
>
>     Extend dired-do-shell-command substitutions
>     
>     Substitute "`?`" inside command with the current file name.
>     * lisp/dired-aux.el (dired-quark-subst-regexp, dired-star-subst-regexp):
>     Delete them.

> diff --git a/lisp/dired-aux.el b/lisp/dired-aux.el
> index 121bebeb65..1265fe3501 100644
> --- a/lisp/dired-aux.el
> +++ b/lisp/dired-aux.el
> @@ -49,8 +49,30 @@ dired-create-files-failures
>  ;;;###begin dired-cmd.el
>  ;; Diffing and compressing
>  
> -(defconst dired-star-subst-regexp "\\(^\\|[ \t]\\)\\*\\([ \t]\\|$\\)")
> -(defconst dired-quark-subst-regexp "\\(^\\|[ \t]\\)\\?\\([ \t]\\|$\\)")
> +(defun dired-isolated-string-re (string)
> +  "Return a regexp to match STRING isolated.

I am wondering if i should keep these variables in case some
code out there rely on them; something like adding a comment saying that
these vars are obsolete? Or is OK just to drop these vars?



      reply	other threads:[~2017-07-01  5:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-26 15:38 26.0.50; Extend dired-do-shell-command substitutions Tino Calancha
2017-07-01  5:06 ` Tino Calancha [this message]

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=87k23srbk6.fsf@calancha-pc \
    --to=tino.calancha@gmail.com \
    --cc=emacs-devel@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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).