Just recently tried using
locate foo.conf | cd
to automagically move to the directory in which I've saved foo.conf
Of course it didn't work as you can't cd to /bar/foo.conf
I didn't find a way to dropping the actual file name from the result of
locate.
I did a brief google on locate, but didn't
On Fri, 11 May 2007 14:34:44 +0200, Martin S wrote:
> Just recently tried using
>
> locate foo.conf | cd
>
> to automagically move to the directory in which I've saved foo.conf
> Of course it didn't work as you can't cd to /bar/foo.conf
>
> I didn't find a way to dropping the actual file name f
On Friday 11 May 2007 14:34, Martin S wrote:
> Just recently tried using
>
> locate foo.conf | cd
>
> to automagically move to the directory in which I've saved foo.conf
> Of course it didn't work as you can't cd to /bar/foo.conf
It would not have worked anyway, since cd does not read its input f
On Fri, 11 May 2007 15:29:03 +0200, Martin S wrote:
> A bit much to typw though. Don't know if I'd save much time from first
> doing a locate and the manually typing the cd [result] string :)
Or type "cd "
PS - please don't top-post.
--
Neil Bothwick
Two is not equal to three, even for larg
On Fri, 11 May 2007 15:53:42 +0200, Martin S wrote:
> Forgot you're still toppost sensitive in this group.
And always will be, once oyu've seen the one true way you don't change :)
> Anyway I don't have a mouse on that system, so I'll have to use Alan
> suggestion.
You could use a script. e.g.
Martin S writes:
Anyway I don't have a mouse on that system, so I'll have to use Alan
suggestion.
You could use a little shell function like this one. Add it to your
~/.bashrc or somewhere like that.
locatecd()
{
oldIFS=$IFS
IFS=$'\n'
results=( $( locate "$1" ) )
That works yes.
A bit much to typw though. Don't know if I'd save much time from first doing
a locate and the manually typing the cd [result] string :)
Martin S
2007/5/11, Neil Bothwick <[EMAIL PROTECTED]>:
On Fri, 11 May 2007 14:34:44 +0200, Martin S wrote:
> Just recently tried using
>
> lo
2007/5/11, Neil Bothwick <[EMAIL PROTECTED]>:
On Fri, 11 May 2007 15:29:03 +0200, Martin S wrote:
> A bit much to typw though. Don't know if I'd save much time from first
> doing a locate and the manually typing the cd [result] string :)
Or type "cd "
Forgot you're still toppost sensitive
On 11 May 2007, Martin S wrote:
> That works yes.
> A bit much to typw though. Don't know if I'd save much time from first
> doing a locate and the manually typing the cd [result] string :)
Make it a shell function if you need it often.
Uwe
--
The Informal Linux Group Namibia:
http://www.linux.
On Friday 11 May 2007 16:09:40 Neil Bothwick wrote:
> > Anyway I don't have a mouse on that system, so I'll have to use Alan
> > suggestion.
>
> You could use a script. e.g.
A script won't help as it will only change the path in the context of the
script. A shell function is required.
--
Bo And
Hello Bo Ørsted Andresen,
> A script won't help as it will only change the path in the context of
> the script. A shell function is required.
It would work if you sourced it, but a shell function would be better.
--
Neil Bothwick
WinErr 020: Error recording error codes - Additional errors wil
Yes, I run as root: updatedb
But when run:
locate consent_extraction*
It only list one file:
/home/fd/consent_extraction1.pdf (this is a link file)
/home/fd/business/forms/consent_extraction1.pdf
It can not find: "consent_extraction.pdf" both files are in same directory
ll business/forms/
total
Hi,
this morning my akregator didn't want to weak up.
So, I launched it from konsole and as I saw no output, I decide to
rebuild it (I've been playing around with some use flags, adding,
removing...)
#eix akregator
* kde-base/akregator
Available versions: 3.4.3 3.5.2 ~3.5.3
Installed:
On mer. 15 mars 09:10:26 2017, the...@sys-concept.com wrote:
> Yes, I run as root: updatedb
> But when run:
> locate consent_extraction*
>
> It only list one file:
> /home/fd/consent_extraction1.pdf (this is a link file)
> /home/fd/business/forms/consent_extraction1.pdf
>
> It can not find: "cons
On 03/15/2017 09:31 AM, Alarig Le Lay wrote:
> On mer. 15 mars 09:10:26 2017, the...@sys-concept.com wrote:
>> Yes, I run as root: updatedb
>> But when run:
>> locate consent_extraction*
>>
>> It only list one file:
>> /home/fd/consent_extraction1.pdf (this is a link file)
>> /home/fd/business/form
On 03/15/2017 09:51 AM, the...@sys-concept.com wrote:
[snip]
>>
>> Do you have file consent_extraction1.pdf in your working directory? In
>> that case, your shell will begin by expending your asterisk and you will
>> really look for consent_extraction1.pdf.
>
> It is a strange behaviour :-/
> Yes,
On Wed, 15 Mar 2017 09:10:26 -0600, the...@sys-concept.com wrote:
> Yes, I run as root: updatedb
> But when run:
> locate consent_extraction*
>
> It only list one file:
> /home/fd/consent_extraction1.pdf (this is a link file)
> /home/fd/business/forms/consent_extraction1.pdf
The wildcard is bein
On 03/15/2017 10:16 AM, Neil Bothwick wrote:
> On Wed, 15 Mar 2017 09:10:26 -0600, the...@sys-concept.com wrote:
>
>> Yes, I run as root: updatedb
>> But when run:
>> locate consent_extraction*
>>
>> It only list one file:
>> /home/fd/consent_extraction1.pdf (this is a link file)
>> /home/fd/busin
On Wed, 15 Mar 2017 10:24:27 -0600, the...@sys-concept.com wrote:
> > The wildcard is being expanded by your shell, so the command you are
> > actually running is
> >
> > locate consent_extraction1.pdf
> >
> > If you want to pass the * to locate, you need to escape or quote it.
>
> locate co
On 15/03/2017 18:03, the...@sys-concept.com wrote:
> On 03/15/2017 09:51 AM, the...@sys-concept.com wrote:
> [snip]
>>>
>>> Do you have file consent_extraction1.pdf in your working directory? In
>>> that case, your shell will begin by expending your asterisk and you will
>>> really look for consent
On Thu, 13 Jul 2006 09:43:03 +0200
Arnau Bria wrote:
> #eix akregator
> * kde-base/akregator
> Available versions: 3.4.3 3.5.2 ~3.5.3
> Installed: 3.4.3 3.5.2
>
> (Why do I have 2 akregators?)
Ok, I did not notice that it refers to kde-base...
--
Arnau Bria
http://blog.eme
On 7/13/06, Arnau Bria <[EMAIL PROTECTED]> wrote:
Then, after akregator compilation, I was looking for some warning and I
found a message that toke me to
I suggest to post the actual warning message[s], and your emerge --info output.
-Richard
--
gentoo-user@gentoo.org mailing list
On Thu, 13 Jul 2006 11:12:43 -0700
Richard Fish wrote:
> On 7/13/06, Arnau Bria <[EMAIL PROTECTED]> wrote:
> > Then, after akregator compilation, I was looking for some warning
> > and I found a message that toke me to
>
> I suggest to post the actual warning message[s], and your emerge
> --info
On 7/14/06, Arnau Bria <[EMAIL PROTECTED]> wrote:
CFLAGS="-march=pentium4 -O2 -pipe -fomit-frame-pointer -mtune=i686"
CXXFLAGS="-O2 -mcpu=i686 -pipe"
Hrm, these are really not sane. -march is telling gcc to build C code
that will only run on a p4, and then you have -mtune specifying to run
on
On Fri, 14 Jul 2006 01:30:49 -0700
Richard Fish wrote:
> On 7/14/06, Arnau Bria <[EMAIL PROTECTED]> wrote:
> > CFLAGS="-march=pentium4 -O2 -pipe -fomit-frame-pointer -mtune=i686"
> > CXXFLAGS="-O2 -mcpu=i686 -pipe"
>
> Hrm, these are really not sane. -march is telling gcc to build C code
> that
"Richard Fish" <[EMAIL PROTECTED]> writes:
> Hrm, these are really not sane. -march is telling gcc to build C code
> that will only run on a p4, and then you have -mtune specifying to run
> on everything back to a pentium-II. I *think* -march takes precedence
> here
Does it? I would have th
On 7/14/06, Graham Murray <[EMAIL PROTECTED]> wrote:
"Richard Fish" <[EMAIL PROTECTED]> writes:
> Hrm, these are really not sane. -march is telling gcc to build C code
> that will only run on a p4, and then you have -mtune specifying to run
> on everything back to a pentium-II. I *think* -marc
27 matches
Mail list logo
