Prev: How to render text in image photo
Next: freewrap ico
From: Arjen Markus on 18 Jun 2010 03:19
Hi,

we ran into a small issue with [exec] on Windows:
In a DOS-box you can simply type a.cmd and the batch file is run. But
[exec]
gives the message:

couldn't execute "a.cmd": no such file or directory

[auto_execok a.cmd] simply returns "./a.cmd" and that gives the same
message.

You can run it by explicitly running it via cmd.exe:

exec cmd.exe /c a.cmd

It seems a bug (or perhaps better: an omission) in auto_execok.

Any thoughts?

Regards,

Arjen
From: Harald Oehlmann on 18 Jun 2010 03:32
On 18 Jun., 09:19, Arjen Markus <arjen.markus...(a)gmail.com> wrote:
> Hi,
>
> we ran into a small issue with [exec] on Windows:
> In a DOS-box you can simply type a.cmd and the batch file is run. But
> [exec]
> gives the message:
>
> couldn't execute "a.cmd": no such file or directory
>
> [auto_execok a.cmd] simply returns "./a.cmd" and that gives the same
> message.
>
> You can run it by explicitly running it via cmd.exe:
>
> exec cmd.exe /c a.cmd
>
> It seems a bug (or perhaps better: an omission) in auto_execok.
>
> Any thoughts?

Because it works with a.bat, I would file a bug report....

Regards,
Harald
From: Arjen Markus on 18 Jun 2010 07:36
On 18 jun, 09:32, Harald Oehlmann <wortka...(a)yahoo.de> wrote:
> On 18 Jun., 09:19, Arjen Markus <arjen.markus...(a)gmail.com> wrote:
>
>
>
>
>
> > Hi,
>
> > we ran into a small issue with [exec] on Windows:
> > In a DOS-box you can simply type a.cmd and the batch file is run. But
> > [exec]
> > gives the message:
>
> > couldn't execute "a.cmd": no such file or directory
>
> > [auto_execok a.cmd] simply returns "./a.cmd" and that gives the same
> > message.
>
> > You can run it by explicitly running it via cmd.exe:
>
> > exec cmd.exe /c a.cmd
>
> > It seems a bug (or perhaps better: an omission) in auto_execok.
>
> > Any thoughts?
>
> Because it works with a.bat, I would file a bug report....
>
> Regards,
> Harald- Tekst uit oorspronkelijk bericht niet weergeven -
>
> - Tekst uit oorspronkelijk bericht weergeven -

I will do so.

Regards,

Arjen
From: Arjen Markus on 18 Jun 2010 07:43
On 18 jun, 13:36, Arjen Markus <arjen.markus...(a)gmail.com> wrote:
> On 18 jun, 09:32, Harald Oehlmann <wortka...(a)yahoo.de> wrote:
>
>
>
>
>
> > On 18 Jun., 09:19, Arjen Markus <arjen.markus...(a)gmail.com> wrote:
>
> > > Hi,
>
> > > we ran into a small issue with [exec] on Windows:
> > > In a DOS-box you can simply type a.cmd and the batch file is run. But
> > > [exec]
> > > gives the message:
>
> > > couldn't execute "a.cmd": no such file or directory
>
> > > [auto_execok a.cmd] simply returns "./a.cmd" and that gives the same
> > > message.
>
> > > You can run it by explicitly running it via cmd.exe:
>
> > > exec cmd.exe /c a.cmd
>
> > > It seems a bug (or perhaps better: an omission) in auto_execok.
>
> > > Any thoughts?
>
> > Because it works with a.bat, I would file a bug report....
>
> > Regards,
> > Harald- Tekst uit oorspronkelijk bericht niet weergeven -
>
> > - Tekst uit oorspronkelijk bericht weergeven -
>
> I will do so.
>
> Regards,
>
> Arjen- Tekst uit oorspronkelijk bericht niet weergeven -
>
> - Tekst uit oorspronkelijk bericht weergeven -

Done - bug #3017997

Regards,

Arjen
From: Donal K. Fellows on 18 Jun 2010 08:47
On 18 June, 08:19, Arjen Markus <arjen.markus...(a)gmail.com> wrote:
> Any thoughts?

It's fixed now, but you can work around this by setting the standard
Windows PATHEXT environment variable before Tcl starts.

Donal.
 | 
Pages: 1
Prev: How to render text in image photo
Next: freewrap ico