Your message dated Wed, 30 Apr 2008 02:06:03 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#420207: wine: Missing desktop / file manager
integration
has caused the Debian Bug report #420207,
regarding wine: Missing desktop / file manager integration
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
420207: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=420207
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: wine
Version: 0.9.31-1
Severity: normal
Tags: patch
Currently, Wine has problems launching Windows applications associated
with file types registered by Windows programs, and it also lacks
integration with file managers to start a Windows program when a user
opens a file.
The first problem is caused by the misinterpretation of a starting slash
in the pathname:
$ wine start /some/dir/file.txt
doesn't open Notepad but gives usage info on start.exe instead, whereas
$ wine start file.txt
works as expected.
The second problem is the inconvenience of having to specify the full
path to the Windows application for each file type that a user wishes to
register.
Please consider the included script 'wine-start' which will launch the
Windows application associated with the file type of the specified file,
and which also handles the leading slash problem. I think integrating
this with the Debian menu system shouldn't be a problem at all.
Please feel free to send my patch upstream if you like it.
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1,
'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.18-4-686 (SMP w/1 CPU core)
Locale: LANG=nl_NL.UTF-8, LC_CTYPE=nl_NL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages wine depends on:
ii debconf [debconf-2.0] 1.5.13 Debian configuration management sy
ii libwine 0.9.31-1 Windows API Implementation (Librar
ii xbase-clients 1:7.1.ds1-2 miscellaneous X clients
Versions of packages wine recommends:
ii msttcorefonts 1.8 Installer for Microsoft TrueType c
ii wine-utils 0.9.31-1 Windows API Implementation (Utilit
-- debconf information:
wine/del_wine_conf: true
wine/install_type: Autodetect
wine-start
Description: application/shellscript
--- End Message ---
--- Begin Message ---
Version: 0.9.60-1
Alain Kalker skrev:
On Tue, 2008-01-01 at 05:36 +0100, Ove Kaaven wrote:
Alain Kalker skrev:
Package: wine
Version: 0.9.31-1
Severity: normal
Tags: patch
Currently, Wine has problems launching Windows applications associated
with file types registered by Windows programs, and it also lacks
integration with file managers to start a Windows program when a user
opens a file.
I'm not entire sure what you mean here. Do you mean file associations
that you add manually to your file managers, or file associations to be
added automatically by Wine? I don't think Wine creates them
automatically, and it probably shouldn't, either (things could probably
get really annoying if it did).
I meant that it should be possible for file associations created by
Windows applications (to open documents that they support) to be
exported to file managers (probably after user confirmation).
Well, like I said, I don't think Wine should. You probably want .txt
files to be opened by your preferred editor (like gedit), not by
Notepad, for example. And there's no obvious place to hook into anything
either, because file associations are just data in the registry that's
looked up on-demand, apps don't call a special API to create them. "User
confirmation" would be tricky.
But if you think there's a sane way, you're welcome to submit patches to
Wine...
The first problem is caused by the misinterpretation of a starting slash
in the pathname:
$ wine start /some/dir/file.txt
doesn't open Notepad but gives usage info on start.exe instead, whereas
$ wine start file.txt
works as expected.
If you need to use the full path, the ideal way would be to use
$ wine start `winepath -w /some/dir/file.txt`
Thanks, that fixes this problem.
In 0.9.60, there's now another way:
$ wine start /unix /some/dir/file.txt
I think I'll consider it enough for closing this bug.
> Sadly, winepath has no manpage (I could
> file a separate bug report on that),
There are enough missing-manpage bugs on wine, now if only someone would
actually *write* any of them...
--- End Message ---
