On Sat, 5 Feb 2011 21:49:30 -0500
Albert Lee wrote:
>
> I think relying on tilde expansion can can be considered
> good practice for the interactive use case.
>
Tilde expansion doesn't work if there are quotes around the path, and if you
search the forum, you will find instances of users who d
On Sat, Feb 05, 2011 at 09:49:30PM -0500, Albert Lee wrote:
>
> Anyone using the original Bourne sh *interactively* is in for a world
> of pain anyway (speaking as someone who often had to before the ksh93
> replacement). I think relying on tilde expansion can can be considered
> good practice for
On 02/05/2011 07:54 PM, Albert Lee wrote:
Instead, I am suggesting reducing the complexity of the solution,
Multiple expansions, redirections and use of xargs is hardly a
simplification of a script with 2 parameters.
Again, we are not talking about advanced skills here. We talking about users
On Thu, Feb 3, 2011 at 9:49 PM, Vitaliy Margolen
wrote:
> On 02/03/2011 09:17 AM, Albert Lee wrote:
>>
>> The instructions were intended to give some context for users who
>> might not be familiar with the ~ expansion.
>
> Then mention that if you must. "~" is used in number of other places in FAQ
On Sat, Feb 5, 2011 at 3:05 AM, Gert van den Berg wrote:
> On Thu, Feb 3, 2011 at 18:17, Albert Lee wrote:
>> The instructions were intended to give some context for users who
>> might not be familiar with the ~ expansion.
>
> Using {$HOME} would be more portable. The Bourne shell (/bin/sh) on
>
On Sat, Feb 05, 2011 at 10:14:07AM +0200, Gert van den Berg wrote:
> On Sat, Feb 5, 2011 at 10:05, Gert van den Berg wrote:
> > On Thu, Feb 3, 2011 at 18:17, Albert Lee wrote:
> >> The instructions were intended to give some context for users who
> >> might not be familiar with the ~ expansion.
>
On Sat, Feb 5, 2011 at 10:05, Gert van den Berg wrote:
> On Thu, Feb 3, 2011 at 18:17, Albert Lee wrote:
>> The instructions were intended to give some context for users who
>> might not be familiar with the ~ expansion.
>
> Using {$HOME} would be more portable.
And using "${WINEPREFIX:-${HOME}/
On Thu, Feb 3, 2011 at 18:17, Albert Lee wrote:
> The instructions were intended to give some context for users who
> might not be familiar with the ~ expansion.
Using {$HOME} would be more portable. The Bourne shell (/bin/sh) on
Solaris (9/10 - OpenSolaris defaulted to ksh) doesn't support ~
(al
Correction:
${HOME}
On 02/03/2011 09:17 AM, Albert Lee wrote:
The instructions were intended to give some context for users who
might not be familiar with the ~ expansion.
Then mention that if you must. "~" is used in number of other places in FAQ,
and all over the net. Please keep it simple.
It's a fairly trivi
On Thu, Feb 3, 2011 at 12:32 PM, David Laight wrote:
> On Thu, Feb 03, 2011 at 11:17:39AM -0500, Albert Lee wrote:
>>
>> >
>> >> ?It's exec(2)'ed so it doesn't matter what the program is.
>> >
>> > Basically run in a shell. So you need an extra wrapper (env) why?
>>
>> To handle PATH search, since
On Thu, Feb 03, 2011 at 11:17:39AM -0500, Albert Lee wrote:
>
> >
> >> ?It's exec(2)'ed so it doesn't matter what the program is.
> >
> > Basically run in a shell. So you need an extra wrapper (env) why?
>
> To handle PATH search, since Wine requires an absolute path. This is a
> common trick use
On Thu, Feb 3, 2011 at 12:13 AM, Vitaliy Margolen
wrote:
> On 02/02/2011 09:52 PM, Albert Lee wrote:
>>
>> I meant 'cd' is the command preceding this one in the block this is a
>> part of, if you look at the context.
>
> Then you should remove that cd instead. Starting instructions from "go to
> y
On 02/02/2011 09:52 PM, Albert Lee wrote:
I meant 'cd' is the command preceding this one in the block this is a
part of, if you look at the context.
Then you should remove that cd instead. Starting instructions from "go to
your home directory" just to jump somewhere else doesn't make much sense.
On Wed, Feb 2, 2011 at 1:52 AM, Vitaliy Margolen
wrote:
> On 02/01/2011 09:47 PM, Albert Lee wrote:
>>
>> On Sat, Jan 29, 2011 at 4:36 PM, Vitaliy wrote:
-cd ~/.wine/drive_c/Program\ Files
+cd .wine/drive_c/Program\ Files
>>>
>>> This will break if current directory is not $HOME.
>
On 02/02/2011 08:10 AM, Albert Lee wrote:
I notice you reverted the changes after I addressed these issues, care
to explain why?
See my response from yesterday.
Vitaliy.
On Wed, 2 Feb 2011 10:09:16 -0500
Albert Lee wrote:
> The Open Group even more strongly objects to the phrase "Unix-like".
>
They also state explicitly on their website that Linux is not Unix.
http://www.unix.org/what_is_unix/flavors_of_unix.html
Ozan's suggestion of "Posix-compatible" is more
I notice you reverted the changes after I addressed these issues, care
to explain why?
On Tue, Feb 1, 2011 at 11:47 PM, Albert Lee wrote:
> On Sat, Jan 29, 2011 at 4:36 PM, Vitaliy wrote:
>> On 01/29/2011 12:21 PM, Dan Kegel wrote:
>>>
>>> Hi Albert,
>>> http://wiki.winehq.org/FAQ?action=diff&re
On Wed, Feb 2, 2011 at 8:03 AM, Rosanne DiMesio wrote:
> On Sat, 29 Jan 2011 13:18:40 -0500
> Albert Lee wrote:
>
>>
>> I notice you have reverted my edits to the FAQ on the wiki (
>> http://wiki.winehq.org/FAQ?action=info ). As I was trying to clarify
>> the shell metacharacter information and o
On Sat, 29 Jan 2011 13:18:40 -0500
Albert Lee wrote:
>
> I notice you have reverted my edits to the FAQ on the wiki (
> http://wiki.winehq.org/FAQ?action=info ). As I was trying to clarify
> the shell metacharacter information and operating system/platform
> support, and add new file association
On 02/01/2011 09:47 PM, Albert Lee wrote:
On Sat, Jan 29, 2011 at 4:36 PM, Vitaliy wrote:
-cd ~/.wine/drive_c/Program\ Files
+cd .wine/drive_c/Program\ Files
This will break if current directory is not $HOME.
'cd' immediately precedes this.
That still doesn't make the command valid. It won
On Sat, Jan 29, 2011 at 4:36 PM, Vitaliy wrote:
> On 01/29/2011 12:21 PM, Dan Kegel wrote:
>>
>> Hi Albert,
>> http://wiki.winehq.org/FAQ?action=diff&rev2=384&rev1=383 looks
>> like it was a pretty big edit.
>>
>> Try smaller ones, and try to do just one kind of change per edit.
>
> That, and the
On 01/29/2011 12:21 PM, Dan Kegel wrote:
Hi Albert,
http://wiki.winehq.org/FAQ?action=diff&rev2=384&rev1=383 looks
like it was a pretty big edit.
Try smaller ones, and try to do just one kind of change per edit.
That, and the fact that some changes where questionable, and broken:
-cd ~/.wine
Hi Albert,
http://wiki.winehq.org/FAQ?action=diff&rev2=384&rev1=383 looks
like it was a pretty big edit.
Try smaller ones, and try to do just one kind of change per edit.
Hi Vitaliy,
I notice you have reverted my edits to the FAQ on the wiki (
http://wiki.winehq.org/FAQ?action=info ). As I was trying to clarify
the shell metacharacter information and operating system/platform
support, and add new file association instructions, I would like to
know why this happened
25 matches
Mail list logo