On Thu, 17 Jan 2008 16:02:53 + (GMT)
Stuart Buchanan <[EMAIL PROTECTED]> wrote:
>
> --- Syd&Sandy wrote:
> > On Thu, 17 Jan 2008 12:06:54 +0100
> > Melchior FRANZ wrote:
> > > OK, to be honest: the change disturbed me as well:
> > >
> > > /instrumentation/vertical-speed-indicator/indicated
--- Syd&Sandy wrote:
> On Thu, 17 Jan 2008 12:06:54 +0100
> Melchior FRANZ wrote:
> > OK, to be honest: the change disturbed me as well:
> >
> > /instrumentation/vertical-speed-indicator/indicated-speed-fpm
> > to
> > /instrumentation/inst-vertical-speed-indicator/indicated-speed-fpm
> >
On Thu, 17 Jan 2008 12:06:54 +0100
Melchior FRANZ <[EMAIL PROTECTED]> wrote:
>
> * Syd&Sandy -- Thursday 17 January 2008:
> > Charming , as always :)
>
> :-P
>
> Note that it didn't disturb me at all that you broke something --
> that happens to everyone. The more you do, the more you break
> o
On Jan 17, 2008 4:13 AM, Stefan Seifert <[EMAIL PROTECTED]> wrote:
> Curtis Olson wrote:
>
> > Don't bother listening to Melchior, he's busy coming up with absurdly long
> > strings of obscure unix commands that are just a huge waste of time to
> > type. You can do the same check with this much si
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Stefan Seifert wrote:
> Curtis Olson wrote:
>
>> Don't bother listening to Melchior, he's busy coming up with absurdly long
>> strings of obscure unix commands that are just a huge waste of time to
>> type. You can do the same check with this much
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Melchior FRANZ wrote:
| * Stefan Seifert -- Thursday 17 January 2008:
|> find . -name \*.xml | xargs grep vsi-3d
|
| I didn't use this because this puts all file paths into the
| command line buffer, and it depends on the buffer size whether
| it works
* Stefan Seifert -- Thursday 17 January 2008:
> find . -name \*.xml | xargs grep vsi-3d
I didn't use this because this puts all file paths into the
command line buffer, and it depends on the buffer size whether
it works or not (unlike with "while read"). I remember cases
where it didn't work, but
Curtis Olson wrote:
> Don't bother listening to Melchior, he's busy coming up with absurdly long
> strings of obscure unix commands that are just a huge waste of time to
> type. You can do the same check with this much simpler command and save 26
> key strokes (if you start in the aircraft direct
* Syd&Sandy -- Thursday 17 January 2008:
> Charming , as always :)
:-P
Note that it didn't disturb me at all that you broke something --
that happens to everyone. The more you do, the more you break
occasionally. So the rate of breakage is really a good sign, not
a bad one. :-)
Only the explana
On Wed, 16 Jan 2008 21:46:05 -0600
"Curtis Olson" <[EMAIL PROTECTED]> wrote:
> On Jan 16, 2008 7:23 PM, Syd&Sandy wrote:
>
> > On Wed, 16 Jan 2008 21:19:32 +0100
> > Melchior FRANZ wrote:
> >
> > > * Syd&Sandy -- Wednesday 16 January 2008:
> > > > I rarely get time to check other's work , so I ne
On Jan 16, 2008 7:23 PM, Syd&Sandy wrote:
> On Wed, 16 Jan 2008 21:19:32 +0100
> Melchior FRANZ wrote:
>
> > * Syd&Sandy -- Wednesday 16 January 2008:
> > > I rarely get time to check other's work , so I never know who
> > > else is using the gauges ...
> >
> > Sorry, but that's absurd. It takes a
On Wed, 16 Jan 2008 21:19:32 +0100
Melchior FRANZ <[EMAIL PROTECTED]> wrote:
> * Syd&Sandy -- Wednesday 16 January 2008:
> > I rarely get time to check other's work , so I never know who
> > else is using the gauges ...
>
> Sorry, but that's absurd. It takes almost no time to check ...
>
> $
* Syd&Sandy -- Wednesday 16 January 2008:
> I rarely get time to check other's work , so I never know who
> else is using the gauges ...
Sorry, but that's absurd. It takes almost no time to check ...
$ find $FG_ROOT/Aircraft -name \*.xml|while read i; do grep -l vsi-3d.xml $i;
done
/usr/loc
On Wed, 16 Jan 2008 14:42:20 + (GMT)
Stuart Buchanan <[EMAIL PROTECTED]> wrote:
> Hi All,
>
> I've been tracking down why the VSI on the pittss1c has stopped working. It
> uses
> the Aircraft/Instruments-3d/vsi-6/vsi-3d.xml model.
>
> Looking at the change log, there was a change in the pro
Hi All,
I've been tracking down why the VSI on the pittss1c has stopped working. It uses
the Aircraft/Instruments-3d/vsi-6/vsi-3d.xml model.
Looking at the change log, there was a change in the property it uses from
/instrumentation/vertical-speed-indicator/indicated-speed-fpm
to
/instrument
15 matches
Mail list logo