emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Re: Erroneous "No such file or directory" with babel and remote dir
Date: Thu, 15 Nov 2012 19:31:48 +0100	[thread overview]
Message-ID: <87haoq1zvv.fsf@Rainer.invalid> (raw)
In-Reply-To: 6907.1352962529@alphaville

Nick Dokos writes:
> The first set of code transformations (implemented as commit
> 63b5f8f2e85b3059a2d30041db6939347a7a2d7d) dealt with the situation by
> doing a mass substitution: flet --> org-flet and labels --> org-labels
> (and in at least one case, flet --> org-labels to deal with a
> recursive definition - I presume that was a preexisting bug that was
> fixed by this substitution) and adding compatibility aliases in
> org-compat.el to use the cl-flet/cl-labels macros from cl.el in emacs
> versions >= 24.1.50.

As has slowly transpired in the meantime, there is no substitution for
the deprecated flet.  The new cl-flet does lexical instead of dynamical
binding of the function slot and the other alternatives have other
subtle differences that don't really seem to be documented in a single

> So the moral of the story is that the code transformations have *not*
> left functionality unchanged. Something went awry but to be honest, I
> don't know what. I didn't spend much time on it because of what I
> found out next.
> And is this the only problem? Probably not: every flet->let
> transformation would have to be scrutinized.

Thanks for this extensive explanation.  I don't know if that might
convince Stefan Monnier to un-deprecate letf, you'd not be the only one
to be rattling his cage on this issue.

+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Waldorf MIDI Implementation & additional documentation:

  reply	other threads:[~2012-11-15 18:32 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-10 14:36 Erroneous "No such file or directory" with babel and remote dir Loris Bennett
2012-09-10 14:42 ` Loris Bennett
2012-09-19  7:37 ` Bastien
2012-09-25 14:11   ` Loris Bennett
2012-09-25 15:30     ` Memnon Anon
2012-09-25 19:54     ` Achim Gratz
2012-09-26  6:56       ` Loris Bennett
2012-09-26  7:14         ` Bastien
2012-09-26 12:10   ` Loris Bennett
2012-09-26 18:09     ` Achim Gratz
2012-09-26 18:38       ` Nick Dokos
2012-09-26 18:57       ` Loris Bennett
2012-09-26 20:06         ` Achim Gratz
2012-09-27  6:38           ` Loris Bennett
2012-09-27 17:22             ` Achim Gratz
2012-11-13 15:16               ` Loris Bennett
2012-11-14  5:04                 ` Nick Dokos
2012-11-14  6:23                   ` Nick Dokos
2012-11-14  7:48                     ` Loris Bennett
2012-11-14 19:47                     ` Nick Dokos
2012-11-15  6:55                     ` Nick Dokos
2012-11-15 18:31                       ` Achim Gratz [this message]
2012-11-14  7:28                   ` Loris Bennett
2012-11-13 15:39               ` Loris Bennett

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:

  List information: https://www.orgmode.org/

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

  git send-email \
    --in-reply-to=87haoq1zvv.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --cc=emacs-orgmode@gnu.org \


* 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


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