Thanks for the tip Andrei!
I am not 100% sure it was .bashrc, it could have been some other config
file, but I am pretty sure it was bash related. it is unfortunately on a
long since gone system.
As to my current system, I have just default settings. I have not
altered anything. I have only
On Du, 02 aug 20, 17:34:07, Esteban L wrote:
>
> Last time I had this issue, I remember I had to go into .bashrc and
> add/change something. I just don't know what it was.
Could it be you changed .inputrc and not .bashrc?
Kind regards,
Andrei
--
http://wiki.debian.org/FAQsFromDebianUser
.
But, I did solve this at one point in the past, with a bash profile
change, so I know that is possible.
On 02.08.20 17:49, The Wanderer wrote:
> On 2020-08-02 at 11:34, Esteban L wrote:
>
>> Hello,
>>
>> I use terminal window/bash quite a bit, and have a quirky behavio
On Sun, Aug 02, 2020 at 05:34:07PM +0200, Esteban L wrote:
> Hello,
[...]
> Maybe best description is:
>
> I am tying this senten
>
>
>
> ce, and it's fine...but i
>
>
>
> I backspace now, as I want to replace the above line "and it's fine" and
> what comes after it to change it to "it's
On 2020-08-02 at 11:34, Esteban L wrote:
> Hello,
>
> I use terminal window/bash quite a bit, and have a quirky behavior
> on Debian, at least not on Mac OS terminal window. I think it's just
> a default issue, that can be altered -- as I had the exact same
> problem years ago
Hello,
I use terminal window/bash quite a bit, and have a quirky behavior on
Debian, at least not on Mac OS terminal window. I think it's just a
default issue, that can be altered -- as I had the exact same problem
years ago -- that I was able to resolve, which I again turns up. I
forgot
* On 2020 08 Jul 08:38 -0500, Greg Wooledge wrote:
> There are lots of choices here. And this is with only the login shell
> layer involved -- no X11 or Wayland.
Good points and it must be emphasized that ~/.profile or ~/.bash_profile
are for *login* shells only. Ordinarily shells started from
that sure as hell is
false for X11 sessions.
> There is a caveat! Isn't there always? The comments at the top of
> /etc/skel/.profile note:
>
> # ~/.profile: executed by the command interpreter for login shells.
> # This file is not read by bash(1), if ~/.bash_profile or ~/.ba
(I've not tried it yet
myself).
There is a caveat! Isn't there always? The comments at the top of
/etc/skel/.profile note:
# ~/.profile: executed by the command interpreter for login shells.
# This file is not read by bash(1), if ~/.bash_profile or ~/.bash_login
# exists.
# see /usr/sha
ved. Assuming you're logging in with a "Debian
> X session", a POSIX shell (sh) is used to read most of the config files
> for the Xsession stuff. Bash extensions like exporting functions won't
> be possible at that point.
>
> > - so launch startx, figuring out ov
is used to read most of the config files
for the Xsession stuff. Bash extensions like exporting functions won't
be possible at that point.
> - so launch startx, figuring out over many failures to start "modern"
> "sessions"
Yeah, as I keep saying to others on this list, t
On Mi, 08 iul 20, 10:44:39, Zenaan Harkness wrote:
>
> - so try somewhere in the session startup apps - nope, courdn't
> figure it out at least
For Debian you want ~/.xsessionrc
Kind regards,
Andrei
--
http://wiki.debian.org/FAQsFromDebianUser
signature.asc
Description: PGP signature
On Mi, 08 iul 20, 09:59:52, Zenaan Harkness wrote:
> On Tue, Jul 07, 2020 at 10:29:47AM -0400, Greg Wooledge wrote:
> >
> > $HOME/bin is placed into the user's default PATH by Debian's ~/.profile
> > (the one in /etc/skel/.profile) if it exists at the time the ~/.profile
> > is read, if the
eractive shell to read ~/.profile (along with other
> configuration files).
Some of us use ~/.bash_profile (and even ~/.bash_login) which will
override ~/.profile being read. Of course, you're best reading
man bashfor a fuller story of bash's machinations.
Cheers,
David.
comprehensive overveiw of every possible piece
> of every possible configuration, but it's a starting point.
I faced this issue a few years back, doing a Linux console login (manual crypt
bindmount for $HOME), setting some env functions in BASH, and very naievely
thinking they would appear
On Wed, Jul 08, 2020 at 09:59:52AM +1000, Zenaan Harkness wrote:
> On Tue, Jul 07, 2020 at 10:29:47AM -0400, Greg Wooledge wrote:
> > On Tue, Jul 07, 2020 at 03:17:37PM +0100, Jonathan Dowland wrote:
> > > On Tue, Jul 07, 2020 at 04:14:16PM +0200, Nicolas George wrote:
> > > > cd ~/bin
> > > > ln
Ahh, asked too soon. Thanks Greg.
On Tue, Jul 07, 2020 at 10:16:21AM -0400, Greg Wooledge wrote:
> On Tue, Jul 07, 2020 at 09:57:34AM -0400, Stephen P. Molnar wrote:
> > The Subject line is the problem
>
> Yeah. The Subject: line reveals the problem: you believe that PATH is
> set primarily by
On Tue, Jul 07, 2020 at 10:29:47AM -0400, Greg Wooledge wrote:
> On Tue, Jul 07, 2020 at 03:17:37PM +0100, Jonathan Dowland wrote:
> > On Tue, Jul 07, 2020 at 04:14:16PM +0200, Nicolas George wrote:
> > > cd ~/bin
> > > ln -s ../opt/something/bin/something
> >
> > Not in the default PATH either.
Jonathan Dowland (12020-07-07):
> Not in the default PATH either.
No, but probably one of the first things anybody who has non-elementary
use will have configured anyway.
Regards,
--
Nicolas George
signature.asc
Description: PGP signature
On Tue, Jul 07, 2020 at 03:17:37PM +0100, Jonathan Dowland wrote:
> On Tue, Jul 07, 2020 at 04:14:16PM +0200, Nicolas George wrote:
> > cd ~/bin
> > ln -s ../opt/something/bin/something
>
> Not in the default PATH either.
$HOME/bin is placed into the user's default PATH by Debian's ~/.profile
On Tue, Jul 07, 2020 at 04:14:16PM +0200, Nicolas George wrote:
cd ~/bin
ln -s ../opt/something/bin/something
Not in the default PATH either.
--
Jonathan Dowland
✎j...@debian.org
https://jmtd.net
On Tue, Jul 07, 2020 at 09:57:34AM -0400, Stephen P. Molnar wrote:
> The Subject line is the problem
Yeah. The Subject: line reveals the problem: you believe that PATH is
set primarily by your shell.
It's not. It's set primarily by your method of login, and then by your
session tools, whether
Roberto C. Sánchez (12020-07-07):
> You should add the export command to ~/.bashrc (for it to only be in
> effect for that user)
Except ~/.bashrc is only sourced for interactive shells, it will not be
run when applications are executed by a GUI, for example.
(Also, for some reason, th
On Tue, Jul 07, 2020 at 09:57:34AM -0400, Stephen P. Molnar wrote:
> The Subject line is the problem with my Debian Buster platform. Now from
> Google I see that there has been a change in the way Debian handles this
> problem.
>
I'm not sure what change you are referring to, but from what you
The Subject line is the problem with my Debian Buster platform. Now from
Google I see that there has been a change in the way Debian handles this
problem.
My user path statement is:
comp@AbNormal:~$ echo $PATH
/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
Now I have a number of
On Sat 20 Jun 2020 at 16:51:12 -0600, Tom Dial wrote:
>
>
> On 6/20/20 13:17, Andrei POPESCU wrote:
>
> > On Sb, 20 iun 20, 18:37:31, Brian wrote:
> >> On Sat 20 Jun 2020 at 17:53:56 +0300, Andrei POPESCU wrote:
> >>
> >>> On Vi, 19 iun 20, 15:12:27, Tom Dial wrote:
>
> I notice that
On 6/20/20 13:17, Andrei POPESCU wrote:
> On Sb, 20 iun 20, 18:37:31, Brian wrote:
>> On Sat 20 Jun 2020 at 17:53:56 +0300, Andrei POPESCU wrote:
>>
>>> On Vi, 19 iun 20, 15:12:27, Tom Dial wrote:
I notice that tasksel (= /usr/bin/tasksel) is a Perl program in which it
appears
On Sb, 20 iun 20, 18:37:31, Brian wrote:
> On Sat 20 Jun 2020 at 17:53:56 +0300, Andrei POPESCU wrote:
>
> > On Vi, 19 iun 20, 15:12:27, Tom Dial wrote:
> > >
> > > I notice that tasksel (= /usr/bin/tasksel) is a Perl program in which it
> > > appears the "cmd" to be executed once selections are
On Sat 20 Jun 2020 at 17:53:56 +0300, Andrei POPESCU wrote:
> On Vi, 19 iun 20, 15:12:27, Tom Dial wrote:
> >
> > I notice that tasksel (= /usr/bin/tasksel) is a Perl program in which it
> > appears the "cmd" to be executed once selections are made (line 24 from
> > the end) is
> >
> > apt-get
On Vi, 19 iun 20, 09:30:30, David Wright wrote:
>
> One other benefit: the knowledge and skills you gain in this process
> will be far more transferable than a deeper understanding of the d-i.
> After all, I haven't gained the impression that you're in technical
> charge of rolling out, say, 5000
On Vi, 19 iun 20, 15:12:27, Tom Dial wrote:
>
> I notice that tasksel (= /usr/bin/tasksel) is a Perl program in which it
> appears the "cmd" to be executed once selections are made (line 24 from
> the end) is
>
> apt-get -q -y -o APT::Install-Recommends=true -o \
> APT::Get::AutomaticRemove=true
On Fri 19 Jun 2020 at 15:12:27 -0600, Tom Dial wrote:
> I notice that tasksel (= /usr/bin/tasksel) is a Perl program in which it
> appears the "cmd" to be executed once selections are made (line 24 from
> the end) is
>
> apt-get -q -y -o APT::Install-Recommends=true -o \
>
On 19.06.20 23:12, Tom Dial wrote:
On 6/19/20 09:28, Brian wrote:
On Thu 18 Jun 2020 at 14:15:00 -0500, David Wright wrote:
On Wed 17 Jun 2020 at 20:48:50 (+0100), Brian wrote:
AFAICT, it appears Recommends are *always* installed using the Installer,
irrespective of preseeding. Not
On 6/19/20 09:28, Brian wrote:
> On Thu 18 Jun 2020 at 14:15:00 -0500, David Wright wrote:
>
>> On Wed 17 Jun 2020 at 20:48:50 (+0100), Brian wrote:
>>>
>>> AFAICT, it appears Recommends are *always* installed using the Installer,
>>> irrespective of preseeding. Not *sometimes*.
>>
>> One or
On Fri 19 Jun 2020 at 06:23:00 -0500, Richard Owlett wrote:
> On 06/18/2020 10:25 PM, Andrei POPESCU wrote:
> > On Mi, 17 iun 20, 06:51:18, Richard Owlett wrote:
> > >
> > > The purpose is to determine if I want to do future installs debootstrap.
> > > I attempted to use debootstrap a few years
Hello,
On Fri, Jun 19, 2020 at 09:30:30AM -0500, David Wright wrote:
> Why not start with a minimal working system, even adding a few
> select tools, and then see what isn't necessary for your own
> minimalist system. Now you can try removing them from a *working*
> system and, should you go too
On Thu 18 Jun 2020 at 14:15:00 -0500, David Wright wrote:
> On Wed 17 Jun 2020 at 20:48:50 (+0100), Brian wrote:
> >
> > AFAICT, it appears Recommends are *always* installed using the Installer,
> > irrespective of preseeding. Not *sometimes*.
>
> One or two counterexamples are:
>
>
On Fri 19 Jun 2020 at 06:15:48 +0300, Andrei POPESCU wrote:
> On Mi, 17 iun 20, 20:48:50, Brian wrote:
> >
> > debootstrap is only run during the installation of the base system. It
> > installs recommended packages. That is in contradiction to what the
> > Manual says.
>
> For "regular" use
On Fri 19 Jun 2020 at 06:23:00 (-0500), Richard Owlett wrote:
> On 06/18/2020 10:25 PM, Andrei POPESCU wrote:
> > On Mi, 17 iun 20, 06:51:18, Richard Owlett wrote:
> > >
> > > The purpose is to determine if I want to do future installs debootstrap.
> > > I attempted to use debootstrap a few years
On 06/18/2020 10:25 PM, Andrei POPESCU wrote:
On Mi, 17 iun 20, 06:51:18, Richard Owlett wrote:
The purpose is to determine if I want to do future installs debootstrap.
I attempted to use debootstrap a few years ago and understand it will take
some time/effort to learn it.
If you are going
On Mi, 17 iun 20, 06:51:18, Richard Owlett wrote:
>
> The purpose is to determine if I want to do future installs debootstrap.
> I attempted to use debootstrap a few years ago and understand it will take
> some time/effort to learn it.
If you are going to start from scratch you should consider
On Mi, 17 iun 20, 20:48:50, Brian wrote:
>
> debootstrap is only run during the installation of the base system. It
> installs recommended packages. That is in contradiction to what the
> Manual says.
For "regular" use deboostrap does not install Recommends.
According to the manpage it does
Andersson wrote:
> >>>> On Tue, Jun 16, 2020 at 9:48 PM David Wright
> >>>> wrote:
> >>>>> Where bash-completion does get in the way for me is, for example,
> >>>>> where you download a file that's, say, a PDF but it arrives via wg
On 18/06/2020 21:14, David Wright wrote:
> On Thu 18 Jun 2020 at 20:38:15 (+0100), Darac Marjal wrote:
>> On 18/06/2020 20:15, David Wright wrote:
>>> On Wed 17 Jun 2020 at 10:04:19 (+0200), Anders Andersson wrote:
>>>> On Tue, Jun 16, 2020 at 9:48 PM David Wright
On Thu 18 Jun 2020 at 20:38:15 (+0100), Darac Marjal wrote:
> On 18/06/2020 20:15, David Wright wrote:
> > On Wed 17 Jun 2020 at 10:04:19 (+0200), Anders Andersson wrote:
> >> On Tue, Jun 16, 2020 at 9:48 PM David Wright
> >> wrote:
> >>> Where bas
On 18/06/2020 20:15, David Wright wrote:
> On Wed 17 Jun 2020 at 10:04:19 (+0200), Anders Andersson wrote:
>> On Tue, Jun 16, 2020 at 9:48 PM David Wright
>> wrote:
>>> Where bash-completion does get in the way for me is, for example,
>>> where you d
On Thu 18 Jun 2020 at 06:48:26 (-0500), Richard Owlett wrote:
> On 06/18/2020 03:13 AM, to...@tuxteam.de wrote:
> > On Thu, Jun 18, 2020 at 12:53:55AM +0100, Brian wrote:
> >
> > [...]
> >
> > > No you don't. A user preseeds with
> > >
> > >recommends=false
> > >
> > > But you know for a
On Wed 17 Jun 2020 at 10:04:19 (+0200), Anders Andersson wrote:
> On Tue, Jun 16, 2020 at 9:48 PM David Wright wrote:
> > Where bash-completion does get in the way for me is, for example,
> > where you download a file that's, say, a PDF but it arrives via wget
> > called, sa
On Wed 17 Jun 2020 at 20:48:50 (+0100), Brian wrote:
> On Wed 17 Jun 2020 at 14:15:05 -0500, David Wright wrote:
> > On Wed 17 Jun 2020 at 18:15:49 (+0100), Brian wrote:
> > > > On Wed, Jun 17, 2020 at 06:51:18AM -0500, Richard Owlett wrote:
> >
> > > > > Clarification of my immediate goal:
> > >
On Thu, Jun 18, 2020 at 07:50:39PM +0100, Brian wrote:
> On Thu 18 Jun 2020 at 14:41:19 +0200, to...@tuxteam.de wrote:
>
> > On Thu, Jun 18, 2020 at 06:48:26AM -0500, Richard Owlett wrote:
[...]
> > > 2. Do I "know" something that is not actually true?
> >
> > That is anyone's guess. I know
On Thu 18 Jun 2020 at 14:41:19 +0200, to...@tuxteam.de wrote:
> On Thu, Jun 18, 2020 at 06:48:26AM -0500, Richard Owlett wrote:
> > On 06/18/2020 03:13 AM, to...@tuxteam.de wrote:
> > >On Thu, Jun 18, 2020 at 12:53:55AM +0100, Brian wrote:
> > >
> > >[...]
> > >
> > >>No you don't. A user
Hi,
18 juin 2020 à 09:00 de david...@freevolt.org:
> On Tue, 16 Jun 2020, l0f...@tuta.io wrote:
>
>> 16 juin 2020 à 10:47 de david...@freevolt.org:
>>
>>> I hear some people find bash-completion helpful. Personally, though,
>>> no. Do not want.
>>>
&g
On Thu, Jun 18, 2020 at 06:48:26AM -0500, Richard Owlett wrote:
> On 06/18/2020 03:13 AM, to...@tuxteam.de wrote:
> >On Thu, Jun 18, 2020 at 12:53:55AM +0100, Brian wrote:
> >
> >[...]
> >
> >>No you don't. A user preseeds with
> >>
> >> recommends=false
> >>
> >>But you know for a fact that
On 06/18/2020 03:13 AM, to...@tuxteam.de wrote:
On Thu, Jun 18, 2020 at 12:53:55AM +0100, Brian wrote:
[...]
No you don't. A user preseeds with
recommends=false
But you know for a fact that this doesn't work. Therefore, an answer to
your enquiry
> Is there a way to totally disable
On Thu, Jun 18, 2020 at 07:25:40AM +, davidson wrote:
> On Tue, 16 Jun 2020, l0f...@tuta.io wrote:
[...]
> >Maybe sometimes completion is not working as it should, nothing is
> >perfect, but globally I think that it saves time more than its
> >wastes.
>
> For those it suits, I am glad the
On Thu, Jun 18, 2020 at 12:53:55AM +0100, Brian wrote:
[...]
> No you don't. A user preseeds with
>
> recommends=false
>
> But you know for a fact that this doesn't work. Therefore, an answer to
> your enquiry
>
> > Is there a way to totally disable recommends when installing Debian?
>
>
On Tue, 16 Jun 2020, l0f...@tuta.io wrote:
[dd]
16 juin 2020 à 13:23 de wool...@eeg.ccf.org
It's flaky and full of errors. (Many of these errors end up on the
bash mailing lists as bug reports in bash, but nope, they're from
bash-completion.) It bloats bash, using a lot of memory, and taking
On Tue, 16 Jun 2020, l0f...@tuta.io wrote:
16 juin 2020 à 10:47 de david...@freevolt.org:
I hear some people find bash-completion helpful. Personally, though,
no. Do not want.
Interesting/intriguing point of view.
I will remember this polite new way to call somebody a weirdo.
Why would
On Wed 17 Jun 2020 at 06:31:16 -0500, Richard Owlett wrote:
> On 06/17/2020 06:12 AM, to...@tuxteam.de wrote:
> > On Wed, Jun 17, 2020 at 04:53:45AM -0500, Richard Owlett wrote:
> > > On 06/17/2020 03:34 AM, to...@tuxteam.de wrote:
> > > > [snip]
> > > >
> > > > A couple of those led me to
On Wed 17 Jun 2020 at 14:15:05 -0500, David Wright wrote:
> On Wed 17 Jun 2020 at 18:15:49 (+0100), Brian wrote:
> > > On Wed, Jun 17, 2020 at 06:51:18AM -0500, Richard Owlett wrote:
>
> > > > Clarification of my immediate goal:
> > > >
> > > > Using the ISO of DVD1 I wish to install Debian
On Wed 17 Jun 2020 at 18:15:49 (+0100), Brian wrote:
> > On Wed, Jun 17, 2020 at 06:51:18AM -0500, Richard Owlett wrote:
> > > Clarification of my immediate goal:
> > >
> > > Using the ISO of DVD1 I wish to install Debian with "recommends"
> > > disabled during the installation process.
>
On Wed 17 Jun 2020 at 14:26:31 +0200, to...@tuxteam.de wrote:
> On Wed, Jun 17, 2020 at 06:51:18AM -0500, Richard Owlett wrote:
>
> [...]
>
> > Clarification of my immediate goal:
> >
> > Using the ISO of DVD1 I wish to install Debian with "recommends"
> > disabled during the installation
On 06/17/2020 07:26 AM, to...@tuxteam.de wrote:
On Wed, Jun 17, 2020 at 06:51:18AM -0500, Richard Owlett wrote:
[...]
Clarification of my immediate goal:
Using the ISO of DVD1 I wish to install Debian with "recommends"
disabled during the installation process.
I can't give you an
On Wed, Jun 17, 2020 at 06:51:18AM -0500, Richard Owlett wrote:
[...]
> Clarification of my immediate goal:
>
> Using the ISO of DVD1 I wish to install Debian with "recommends"
> disabled during the installation process.
I can't give you an authoritative answer for this one, sorry.
> The
On 06/17/2020 06:36 AM, to...@tuxteam.de wrote:
On Wed, Jun 17, 2020 at 06:31:16AM -0500, Richard Owlett wrote:
On 06/17/2020 06:12 AM, to...@tuxteam.de wrote:
On Wed, Jun 17, 2020 at 04:53:45AM -0500, Richard Owlett wrote:
On 06/17/2020 03:34 AM, to...@tuxteam.de wrote:
[snip]
A couple of
On Wed, Jun 17, 2020 at 06:31:16AM -0500, Richard Owlett wrote:
> On 06/17/2020 06:12 AM, to...@tuxteam.de wrote:
> >On Wed, Jun 17, 2020 at 04:53:45AM -0500, Richard Owlett wrote:
> >>On 06/17/2020 03:34 AM, to...@tuxteam.de wrote:
> >>>[snip]
> >>>
> >>>A couple of those led me to disable
On 06/17/2020 06:12 AM, to...@tuxteam.de wrote:
On Wed, Jun 17, 2020 at 04:53:45AM -0500, Richard Owlett wrote:
On 06/17/2020 03:34 AM, to...@tuxteam.de wrote:
[snip]
A couple of those led me to disable recommends completely. It seems
I'm a freak monster or sometning ;-@
Is there a way to
On Wed, Jun 17, 2020 at 04:53:45AM -0500, Richard Owlett wrote:
> On 06/17/2020 03:34 AM, to...@tuxteam.de wrote:
> >[snip]
> >
> >A couple of those led me to disable recommends completely. It seems
> >I'm a freak monster or sometning ;-@
> >
>
> Is there a way to totally disable recommends when
On 06/17/2020 03:34 AM, to...@tuxteam.de wrote:
[snip]
A couple of those led me to disable recommends completely. It seems
I'm a freak monster or sometning ;-@
Is there a way to totally disable recommends when installing Debian?
I wish to set up a machine for experimenting to find out what I
On Tue, Jun 16, 2020 at 02:47:38PM -0500, David Wright wrote:
[...]
> Where bash-completion does get in the way for me is, for example,
> where you download a file that's, say, a PDF but it arrives via wget
> called, say, index_0001.3872359.html, for whatever reason.
> So you type
On Tue, Jun 16, 2020 at 9:48 PM David Wright wrote:
> Where bash-completion does get in the way for me is, for example,
> where you download a file that's, say, a PDF but it arrives via wget
> called, say, index_0001.3872359.html, for whatever reason.
> So you type xpdf inde [TAB
backspace by some considerable amount to get to where I'd
> wanted to be.
It seems that I have to press [TAB] more than once for it to complete
the actual filename, but do use [ESC] [BACKSPACE] to rubout by word
rather than character.
But in any case, AIUI most of the above can be co
On 2020-06-16 at 08:57, to...@tuxteam.de wrote:
> On Tue, Jun 16, 2020 at 01:53:59PM +0200, l0f...@tuta.io wrote:
>
> [...]
>
>> Maybe sometimes completion is not working as it should, nothing is
>> perfect, but globally I think that it saves time more than its
>> wastes.
>
> Then just use it
On Tue, Jun 16, 2020 at 01:53:59PM +0200, l0f...@tuta.io wrote:
[...]
> Maybe sometimes completion is not working as it should, nothing is perfect,
> but globally I think that it saves time more than its wastes.
Then just use it and be happy. And just accept that some
(me, among others) are
Hi Greg,
16 juin 2020 à 13:23 de wool...@eeg.ccf.org
> It's flaky and full of errors. (Many of these errors end up on the
> bash mailing lists as bug reports in bash, but nope, they're from
> bash-completion.) It bloats bash, using a lot of memory, and taking
> extra CPU and wal
On Tue, Jun 16, 2020 at 12:54:58PM +0200, l0f...@tuta.io wrote:
> Hi,
>
> 16 juin 2020 à 10:47 de david...@freevolt.org:
>
> > I hear some people find bash-completion helpful. Personally, though,
> > no. Do not want.
> >
> Interesting/intriguing p
Hi,
16 juin 2020 à 10:47 de david...@freevolt.org:
> I hear some people find bash-completion helpful. Personally, though,
> no. Do not want.
>
Interesting/intriguing point of view.
Why would someone not be interested in autocompletion please?
Best regards,
l0f4r0
On Thu, Feb 27, 2020 at 05:13:18PM +0100, Albretch Mueller wrote:
> On 2/27/20, Greg Wooledge wrote:
> > Do you want to search for all files in ~/java whose names end with
> > .java or .txt and which contain the string
> > "java.io.UnsupportedEncodingException;" ?
>
> Yes, I do!
Great!
> But
and which contain the string
> "java.io.UnsupportedEncodingException;" ?
Yes, I do!
> Why is it so hard to write three lines of text that explain what you
> are trying to do?
I thought the bash one liner and my rambing explained it all well.
> Anyway, here's one answer to what I
On Thu, Feb 27, 2020 at 04:46:08PM +0100, Albretch Mueller wrote:
> > We can't really "see what you mean" until you show us. Why don't you
> > just tell us the actual problem? It can't be THAT embarrassing.
>
> OK, here it is again. You will see that as part of the output you
> will see a
> We can't really "see what you mean" until you show us. Why don't you
> just tell us the actual problem? It can't be THAT embarrassing.
OK, here it is again. You will see that as part of the output you
will see a bunch of paths (with the actual matches) that someone were
not picked by the
Not necessarily responding to the appropriate post in this thread, so top
posting to make some general comments:
* Can you do it in two lines (instead of a one liner)? Three lines?
Whatever? If so, if you really want a one liner, develop those multiple lines
and then put them all on one
On Thu, Feb 27, 2020 at 01:40:22PM +0100, Albretch Mueller wrote:
> I need to find all files which names satisfy a pattern and contain a
> certain string, then from those files I need to printf some metadata,
> a la:
>
> find "${_SDIR}" -type f -iregex .*"${_X}" -printf '"%TD
>
On 2/27/20, to...@tuxteam.de wrote:
> On Thu, Feb 27, 2020 at 01:40:22PM +0100, Albretch Mueller wrote:
>> I need to find all files which names satisfy a pattern and contain a
>> certain string, then from those files I need to printf some metadata,
>> a la:
>>
>> find "${_SDIR}" -type f -iregex
On 2/27/2020 6:40 AM, Albretch Mueller wrote:
I need to find all files which names satisfy a pattern and contain a
certain string, then from those files I need to printf some metadata,
a la:
Instead of the lines of the first search by the extensions to look like:
"12/15/18
On Thu, Feb 27, 2020 at 01:40:22PM +0100, Albretch Mueller wrote:
> I need to find all files which names satisfy a pattern and contain a
> certain string, then from those files I need to printf some metadata,
> a la:
>
> find "${_SDIR}" -type f -iregex .*"${_X}" -printf '"%TD
>
I need to find all files which names satisfy a pattern and contain a
certain string, then from those files I need to printf some metadata,
a la:
find "${_SDIR}" -type f -iregex .*"${_X}" -printf '"%TD
%TT",%Ts,%s,"%P"\n' > "${_TMPFL}" 2>&1
I am trying to do all steps in one go, which I think
David Wright wrote:
...
> My question would be:
>
> Which directory is your current directory—what does pwd say?
> After all, the error messages say "reading directory '.': Protocol error",
> and not knowing where you are is unsettling for any command.
in the script i'm using a variable but the
Reco wrote:
> songbird wrote:
...
>> i don't care if it is returned, i just wonder why it isn't
>> redirected to /dev/null like i'm asking it to do.
>
> Because you're redirecting stderr of a wrong process.
> This one-liner should do it.
>
> find . -type f -exec printf %.0s. {} + 2>/dev/null |
ll kinds of error even on a simple opendir(3).
> >
> > Best you can do is to execute:
> >
> > fusermount -u /home/me/pics/camera
>
> i don't care if it is returned, i just wonder why it isn't
> redirected to /dev/null like i'm asking it to do.
>
>
>
On Sat, Feb 01, 2020 at 01:38:55PM -0500, songbird wrote:
> Reco wrote:
> > On Sat, Feb 01, 2020 at 12:36:28PM -0500, songbird wrote:
> >> the directory is a mount point of a device in limbo.
> >> it is showing up as mounted but it really isn't (the
> >> device is turned off).
> > ...
> >>
> >>
ome/me/pics/camera
i don't care if it is returned, i just wonder why it isn't
redirected to /dev/null like i'm asking it to do.
>> i am using the above in a bash script so i don't want
>> any error messages coming from the script itself unless
>> i print them myself.
>
>
e does not work that way. If a userspace backend cannot perform its
function (in this case - a device is disconnected) - it's free to return
all kinds of error even on a simple opendir(3).
Best you can do is to execute:
fusermount -u /home/me/pics/camera
> i am using the above in a bash script so
r to be 0 or the number of files.
i am using the above in a bash script so i don't want
any error messages coming from the script itself unless
i print them myself.
thanks! :)
songbird
On Fri, Dec 13, 2019 at 04:50:18PM -0600, David Wright wrote:
> > PS1='\u@\h $(date +"%d %b %Y %H:%M:%S") :\w\$ '
>
> Could \D{format} not do that?
Oh, good catch. I've... never used that before. ;-) I scanned the
PROMPTING section of the man page too quickly and only saw
the \t \T \@ \A
> if [ "$color_prompt" = yes ]; then
>
> PS1='${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\$
> '
You forgot to add "\d", in PS1 value, that explains different behavior
of prompt in console and Guake.
May be, this could fix the problem
if [
On Fri 13 Dec 2019 at 14:36:09 (-0500), Greg Wooledge wrote:
> On Fri, Dec 13, 2019 at 07:20:53PM +, shirish शिरीष wrote:
> > Can somebody share how can I have a common prompt which is ok both by
> > bash and guake ?
>
> guake...? No idea what that is. apt-cache says
shirish ??? wrote:
> at bottom :-
>
> On 13/12/2019, Dan Ritter wrote:
> > shirish ??? wrote:
> >> Dear all,
> >>
> >> Can somebody share how can I have a common prompt which is ok both by
> >> bash and guake ?
> &g
at bottom :-
On 13/12/2019, Dan Ritter wrote:
> shirish ??? wrote:
>> Dear all,
>>
>> Can somebody share how can I have a common prompt which is ok both by
>> bash and guake ?
>>
>> bash is -
>>
>> $ guake --version
>> Gu
On Fri, Dec 13, 2019 at 07:20:53PM +, shirish शिरीष wrote:
> Can somebody share how can I have a common prompt which is ok both by
> bash and guake ?
guake...? No idea what that is. apt-cache says it's a terminal. So
I'm just going to assume that it works like any other terminal -
401 - 500 of 7373 matches
Mail list logo
