On 04/05/2014 11:18 AM, Massimo Maiurana wrote:
> Pierre Couderc, il 05/04/2014 09:50, ha scritto:
>> Is it possible to start a command when invoking teminology .
> Yes. If you run "terminology -h" you can see all possibile comman d line
> options, including:
>
> -e, --exec command
Pierre Couderc, il 05/04/2014 09:50, ha scritto:
> Is it possible to start a command when invoking teminology .
Yes. If you run "terminology -h" you can see all possibile comman d line
options, including:
-e, --exec command to execute. Defaults to $SHELL (or
passwd shel or /bin/sh)
Is it possible to start a command when invoking teminology .
Such as :
/usr/local/bin/terminology /usr/bin/vim z
or
/usr/local/bin/terminology /usr/bin/vim.sh z
or
/usr/local/bin/terminology "/usr/bin/vim "
--
On 8/26/06, Michael Jennings <[EMAIL PROTECTED]> wrote:
> On Saturday, 26 August 2006, at 19:36:08 (+),
> Asfand Yar Qazi wrote:
>
> > You're getting ruby confused with rails :-)
>
> And you're confusing Perl with Bash.
And you're taking things too seriously.
>
> > I used Ruby here in place o
On Saturday, 26 August 2006, at 19:36:08 (+),
Asfand Yar Qazi wrote:
> You're getting ruby confused with rails :-)
And you're confusing Perl with Bash.
> I used Ruby here in place of Perl, since I don't like the idea of
> running about 5 programs in backquotes and pipes when 1 will do.
Perl
> > >
> > > Just thought it might be useful to someone. If there's a better
> > > solution out there, please tell me!
> >
> > Looks to me like a job for a sed + xargs one-liner(*) to me...
> >
> > (*) left as an exercise for the reader ;-)
>
>
> OK, I got curious as to how easy this would be, so h
On Fri, Aug 25, 2006 at 12:22:47PM +0100, Asfand Yar Qazi wrote:
> I don't know if it's already been done, but here's a little script
> that reads in all key bindings from enlightenment_remote, and
> substitutes all uses of ALT with WIN.
>
> Just thought it might be useful to someone. If there's
On Fri, 25 Aug 2006 12:56:22 +0100 "Asfand Yar Qazi" <[EMAIL PROTECTED]>
wrote:
> On 8/25/06, Asfand Yar Qazi <[EMAIL PROTECTED]> wrote:
> > I don't know if it's already been done, but here's a little script
> > that reads in all key bindings from enlightenment_remote, and
> > substitutes all uses
On 8/25/06, Asfand Yar Qazi <[EMAIL PROTECTED]> wrote:
> I don't know if it's already been done, but here's a little script
> that reads in all key bindings from enlightenment_remote, and
> substitutes all uses of ALT with WIN.
>
> Just thought it might be useful to someone. If there's a better
>
I don't know if it's already been done, but here's a little script
that reads in all key bindings from enlightenment_remote, and
substitutes all uses of ALT with WIN.
Just thought it might be useful to someone. If there's a better
solution out there, please tell me!
#!/usr/bin/ruby -w
DEBUG=fal
I didn't say you should. It was a mistake on my part. I was having
problems with the build process. Some parts weren't building correctly
(evas, ewl), saying they couldn't find dependent parts (ecore,
eet_config). I was trying to troubleshoot this, and I thought using a
different build dir would he
Heh, this script gave me a reason to test my rdiff-backup setup
Here's a hint: Don't use /usr as the build dir.
On Fri, 04 Mar 2005 17:29:04 +0100, Jasper <[EMAIL PROTECTED]> wrote:
> I am working on a webpage for the script. It's now located at
> http://www.shodan.nl/~jasper/e17/. The scri
This saturday I will leave rainy Holland and go, with school, for two
weeks to Italy, in those two weeks I won't have much time I can spend
on-line. So questions about this script will be answered after those two
weeks.
Jasper
---
SF email is
> When I execute script, appears the message bellow:
>
> ./setup: line 62: syntax error near unexpected token `}'
> ./setup: line 62: `}'
It's probably because the scripts we've been posting on here have been
automatically line wrapped. Have you tried getting the one from the
website? I've sent y
Ah, I read your message again, now I see.
Check out version 0.2.8, there it's fixed.
Jasper
david blewett wrote:
I didn't say you should. It was a mistake on my part. I was having
problems with the build process. Some parts weren't building correctly
(evas, ewl), saying they couldn't find dependent
The page is somewhat finished. It is a
http://www.shodan.nl/~jasper/e17/. If you have any suggestions or
comments of any kind, please let me know.
Jasper
Jasper wrote:
I am working on a webpage for the script. It's now located at
http://www.shodan.nl/~jasper/e17/. The script provided in the
d
Why should I now use /usr as the build dir? I built E17 succesfully in
/usr/local/bin/enlightenment-e17/
Jasper
david blewett wrote:
Heh, this script gave me a reason to test my rdiff-backup setup
Here's a hint: Don't use /usr as the build dir.
On Fri, 04 Mar 2005 17:29:04 +0100, Jasper <[E
I am working on a webpage for the script. It's now located at
http://www.shodan.nl/~jasper/e17/. The script provided in the downloads
section works.
Tomorrow I'll finish the page.
Jasper
---
SF email is sponsored by - The IT Product Guide
Read
> great. Wonderfull! Slackware 10.1?
I've had it running fine on 10 and 10.1.
Darrell
---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly li
> I have only tested my script (v0.2.7) using Debian and not yet
> Slackware. But I think it's pretty much Linux distribution independant,
> correct me if I'm wrong.
just to know... I am using the script on Slackware and it works great.
the way you created the script, I believe that it will run on
Benone Marcos wrote:
I have only tested my script (v0.2.7) using Debian and not yet
Slackware. But I think it's pretty much Linux distribution independant,
correct me if I'm wrong.
just to know... I am using the script on Slackware and it works great.
Wonderfull! Slackw
Sure:
#!/bin/sh
#
#Filename: Build-e17.sh
#Version: 0.2.4
#Author: Jasper Lievisse Adriaanse, [EMAIL PROTECTED], copyright
2005, BSD-license.
#Thanks to those on [email protected] who
helped me with this script, especially Benone Marcos.
#
#Before yo
Jasper Lievisse Adriaanse [NedLinux.nl] wrote:
I have only tested my script (v0.2.7) using Debian and not yet
Slackware. But I think it's pretty much Linux distribution independant,
correct me if I'm wrong.
works fine for me under mandrake 10.1
3 We need to start including some text at the s
MillTek wrote:
Jasper,
A couple of issues;
1 Can you produce a 'most-recent' version that has all the changes
that you and the other guys mentioned?
It is a the end of this e-mail. Within some weeks I'll try to make a
simple webpage for it. Then downloading will be easier.
2 You mentioned hav
Can we see the script with these statements in place?
Jim
[EMAIL PROTECTED] wrote:
I just found it out. They should be on line 67 and 77 I think.
Jasper
---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundre
Jasper,
A couple of issues;
1 Can you produce a 'most-recent' version that has all the changes that
you and the other guys mentioned?
2 You mentioned having the Path right. What exactly does this mean? If
we get Path management really worked out we can produce a script that
will build e no m
I now moved all the variables containing $BUILD_DIR to the end of
welke(). Because before that it didn't returned the right value.
Jasper
[EMAIL PROTECTED] wrote:
Darrell Blake wrote:
I also had to add the following lines after setting $BUILD_DIR:
PATH=$PATH:$BUILD_DIR/bin
CPPFLAG
Darrell Blake wrote:
I also had to add the following lines after setting $BUILD_DIR:
PATH=$PATH:$BUILD_DIR/bin
CPPFLAGS=-I$BUILD_DIR/include
oops, and also
LDFLAGS=-I$BUILD_DIR/lib
so entrance can find ecore libraries. And apparently entrance wants to
install /etc/entr
> I also had to add the following lines after setting $BUILD_DIR:
>
> PATH=$PATH:$BUILD_DIR/bin
> CPPFLAGS=-I$BUILD_DIR/include
>
> so headers and config files can be found by subsequent packages.
Yeah I had to too. But to be honest I just ended up building it in
/usr so it wou
I also had to add the following lines after setting $BUILD_DIR:
PATH=$PATH:$BUILD_DIR/bin
CPPFLAGS=-I$BUILD_DIR/include
so headers and config files can be found by subsequent packages.
mark
---
SF email is sponsored by - The IT Pr
Just found another problem. You have to call ruimop() after welke()
otherwise $CVS_SRC doesn't have a value. This is how I have it looking
so far and I'm just about to test it...
#!/bin/sh
#
# General variables are specified below
#
# Flags for GCC, pleae specify your own.
FLAGS="-O3"
# Flags for
I just found it out. They should be on line 67 and 77 I think.
Jasper
> Just having a quick look at your script and it seems you've missed two
> "done" statements on your for loops.
>
> Darrell
>
>
> ---
> SF email is sponsored by - The IT Produ
Just having a quick look at your script and it seems you've missed two
"done" statements on your for loops.
Darrell
---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Dis
Here is the new script, I haven't tested it yet, but it should work.
--
#!/bin/sh
#
# Filename: Build-e17.sh
# Version: 0.2.1
# Author: Jasper Lievisse Adriaanse, [EMAIL PROTECTED], copyright 2005,
BSD-license.
# Thanks to those on enlightenm
Thanks,
so your addition should go between
make distclean &> /dev/null
and
./autogen.sh --prefix=$BUILD_DIR &> $CVS_SRC/logs/$X.log
?
Maybe I'll make a Perl version of it sometime.
Jasper
> nice job Jasper,
>
> works fine here. I just added these lines:
> ...
> LDDFLAGS=-L$BUILD_DIR/lib
...
# gcc flags
FLAGS="-O3 -march=pentium3"
-- added lines --
LDDFLAGS=-L$BUILD_DIR/lib
CPPFLAGS=-L$BUILD_DIR/include
-- added lines --
maak() {
make distclean &> /dev/null
# configure, make, & install with logs
./autogen.sh --prefix=$BUILD_DIR LDFLAGS=$LDFLAGS CPPFLAGS=$CPPFLAGS
&> $CVS_SRC/log
I am now running my script for the first time with having succesfull
thoughts, because when the builddir is the same as the source dir, the
script finishes with 7 minutes on a 1gHz system. That's just to fast. Now
there're results in my build dir and it's taking much more time and
cpu-cycles. So it
There's a small bug in the script, if BUILD_DIR is the same directory as
CVS_SRC, it will remove your freshly downloaded sources because of this
line:
rm -rf $BUILD_DIR/*
please place a # in front of it, or use two different directories.
Jasper
> ...
> # gcc flags
> FLAGS="-O3 -march=pentium3"
> ...
> # gcc flags
> FLAGS="-O3 -march=pentium3"
>
> -- added lines --
> LDDFLAGS=-L$BUILD_DIR/lib
> CPPFLAGS=-L$BUILD_DIR/include
> -- added lines --
>
> maak() {
> make distclean &> /dev/null
>
> # configure, make, & install with logs
> ./autogen.sh --prefix=$BUILD_DIR LDFLAGS=$LDFLAGS CPPFLAGS=
nice job Jasper,
works fine here. I just added these lines:
...
LDDFLAGS=-L$BUILD_DIR/lib
CPPFLAGS=-L$BUILD_DIR/include
...
then, call then in autogen argument list.
thanks for the script
On Tue, 01 Mar 2005 15:29:02 +0100, Jasper <[EMAIL PROTECTED]> wrote:
> Hello,
>
> because I'm getting tir
Hello,
because I'm getting tired of typing the commands for building E17. I
took the script from Edevelop (dated 2002) and updated it. I haven't
tested it yet. But does it _look_ like it'll work?
---build-e17.sh-
#!/bin/sh
# Where the CVS directory is
CVS_SRC=/hom
41 matches
Mail list logo
