From: Lars Ingebrigtsen <larsi@gnus.org>
To: "Tobias" <i@tn-home.de>
Cc: 16454@debbugs.gnu.org
Subject: bug#16454: Enhancement: emacs library jka-compr
Date: Wed, 14 Aug 2019 18:47:31 -0700 [thread overview]
Message-ID: <874l2j8aj0.fsf@mouse.gnus.org> (raw)
In-Reply-To: <003701cf120b$e8d8db60$ba8a9220$@tn-home.de> (Tobias's message of "Wed, 15 Jan 2014 17:07:37 +0100")
"Tobias" <i@tn-home.de> writes:
> The question and answer at
>
> http://stackoverflow.com/questions/21118197/how-to-automatically-decompress-
> a-custom-compressed-file-when-opened-in-emacs/21127244#21127244
>
> show that it would be nice if the arguments of the compression/uncompression
> program would be evaluated.
[...]
> < (defun jka-compr-info-compress-args (info) (aref info 3))
>
> ---
>
>> (defun jka-compr-info-compress-args (info) (mapcar 'apply (aref
> info 3)))
(I'm going through old bug reports that have unfortunately gotten no
responses yet.)
If I understand the patch correctly (it's unfortunately not a context
patch (and has apparently been mangled in transport), which makes it
hard to read), you basically allow the decompressors to be sexps in
addition to strings.
I think if the syntax here is to be extended, I don't think a sexp would
be the best solution -- a function, for instance, seems more natural.
But I also think that this seems like a pretty niche thing to do, and
which can be (as the stackoverflow thread shows) be achieved through
other means, so I don't think this sounds like it's worth adding.
So I'm closing this bug report.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2019-08-15 1:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-15 16:07 bug#16454: Enhancement: emacs library jka-compr Tobias
2019-08-15 1:47 ` Lars Ingebrigtsen [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874l2j8aj0.fsf@mouse.gnus.org \
--to=larsi@gnus.org \
--cc=16454@debbugs.gnu.org \
--cc=i@tn-home.de \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.