Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #98990
| From | eryksun <eryksun@gmail.com> |
|---|---|
| Newsgroups | comp.lang.python |
| Subject | Re: Launcher, and ftype Python.File |
| Date | 2015-11-18 12:03 -0600 |
| Message-ID | <mailman.420.1447869874.16136.python-list@python.org> (permalink) |
| References | <564C32F3.2070909@g.nevcal.com> <mailman.409.1447844007.16136.python-list@python.org> <db3h92Fpu11U1@mid.individual.net> |
On Wed, Nov 18, 2015 at 8:45 AM, Christian Ullrich <chris@chrullrich.net> wrote:
> Apparently %L is always the long file name, and %1 is the short name unless
> the shell can prove that the executable can handle long names.
Specifically old Win16 programs (identified by the file header) aren't
aware of long filenames. In the case of these old programs, the shell
calls GetShortPathName when replacing %0 or %1, but not when replacing
%L.
For Win32 programs %0, %1, and %L are all the same:
C:\Temp>ftype Python.File
Python.File="C:\Windows\py.exe" "%0" "%1" "%L" %*
C:\Temp>longfilename.py
sys.argv:
C:\Temp\longfilename.py
C:\Temp\longfilename.py
C:\Temp\longfilename.py
Short Pathname:
C:\Temp\LONGFI~1.PY
Back to comp.lang.python | Previous | Next — Previous in thread | Find similar | Unroll thread
Re: Launcher, and ftype Python.File Terry Reedy <tjreedy@udel.edu> - 2015-11-18 05:52 -0500
Re: Launcher, and ftype Python.File Christian Ullrich <chris@chrullrich.net> - 2015-11-18 15:45 +0100
Re: Launcher, and ftype Python.File eryksun <eryksun@gmail.com> - 2015-11-18 12:03 -0600
csiph-web