On 16/02/2024 23:35, Franco Martelli wrote:
On 16/02/24 at 03:03, Max Nikulin wrote:
LC_ALL=C.UTF-8 LANGUAGE=it aptitude why firefox-esr
here seems to override, tested twice with "it" and "it_IT.UTF-8":
~# env LC_ALL=C LANGUAGE=it script -T ~/test.time -a ~/test.script
You tested with
wrote:
To change programs' output messages to English LC_MESSAGES=C is often
enough. Sometimes LC_TIME and LC_NUMERIC are required too.
but it seems may have drawbacks if other variables are involved.
From the manual page of "script" command the -t option is deprecated in
favor o
On Fri, Feb 16, 2024 at 11:44:21AM -0500, Greg Wooledge wrote:
> On Fri, Feb 16, 2024 at 05:35:04PM +0100, Franco Martelli wrote:
> > It was stated here:
> > https://lists.debian.org/debian-user/2024/02/msg00592.html
>
> "I think that a recorded session with the output of the commands in
> English
On Fri, Feb 16, 2024 at 05:35:04PM +0100, Franco Martelli wrote:
> It was stated here:
> https://lists.debian.org/debian-user/2024/02/msg00592.html
"I think that a recorded session with the output of the commands in
English is better then a localized session for debugging purposes."
I have troubl
On 16/02/24 at 13:17, Greg Wooledge wrote:
On Fri, Feb 16, 2024 at 09:13:40AM +0200, Teemu Likonen wrote:
In my opinion it's often too much to set LC_ALL=C because it changes
charset to ASCII (LC_CTYPE).
It depends on what you're doing, of course. If the purpose is to
normalize error messages
On Fri, Feb 16, 2024 at 09:13:40AM +0200, Teemu Likonen wrote:
> In my opinion it's often too much to set LC_ALL=C because it changes
> charset to ASCII (LC_CTYPE).
It depends on what you're doing, of course. If the purpose is to
normalize error messages so that you can report your issue to an
En
* 2024-02-15 21:17:44+0100, Franco Martelli wrote:
> Doesn't LC_ALL=C setting override LANG or LANGUAGE settings?
LC_ALL overrides LC_* variables. It's easy to test:
$ locale
LANG=fi_FI.UTF-8
LANGUAGE=fi
LC_CTYPE="fi_FI.UTF-8"
LC_NUMERIC="fi_FI.UTF-8"
LC_TIME="fi_FI.UTF-8
On 16/02/2024 09:34, David Wright wrote:
Yes, LC_ALL=C will override all the locale variables,
but LC_ALL=C.UTF-8 will not:
It is documented in
2.3.3 Specifying a Priority List of Languages
(info "(gettext) The LANGUAGE variable")
https://www.gnu.org/software/gettext/manual/html_node/The-LANG
On Thu 15 Feb 2024 at 21:17:44 (+0100), Franco Martelli wrote:
> On 15/02/24 at 03:28, Max Nikulin wrote:
> > > # env LC_ALL=C script -t 2>~/upgrade-bookwormstep.time -a
> > > ~/upgrade-bookwormstep.script
> >
> > Perhaps LC_ALL=C.UTF-8 is safer. At least several years ago some
> > python scripts
On 16/02/2024 03:17, Franco Martelli wrote:
On 15/02/24 at 03:28, Max Nikulin wrote:
LANG=C.UTF-8; LANGUAGE=; export LANG LANGUAGE
Doesn't LC_ALL=C setting override LANG or LANGUAGE settings?
Sorry, my bad. Of course
LC_ALL=C.UTF-8; LANGUAGE=; export LC_ALL LANGUAGE
and LC_ALL=C
m format is
used on --log-io or when --log-in and --log-out are used together.
See also --logging-format.
One of these paragraphs should give a solution that avoids needing 2>.
The following "script" command syntax should work on all shells (tested
only in Bas
On 14/02/2024 23:11, Franco Martelli wrote:
Well, I'll go with env command syntax for shells portability. I was
asking this because I want to suggest a change to the DDP (Debian
Documentation Project) members for the releases notes documentation ¹
# env LC_ALL=C script -t 2>~
On Wed, Feb 14, 2024 at 09:45:52PM +0100, Franco Martelli wrote:
> A new question arise spontaneously: how can csh users run a "script" saved
> session using "scriptreplay" command? In the §4.4.1 "Recording the session"
> paragraph ¹ I see this syntax:
>
> # scriptreplay ~/upgrade-bookwormstep.ti
On 14/02/24 at 17:48, Greg Wooledge wrote:
On Wed, Feb 14, 2024 at 05:35:59PM +0100, Franco Martelli wrote:
On 14/02/24 at 17:15, Greg Wooledge wrote:
# env LC_ALL=C script -t 2>~/upgrade-bookwormstep.time -a
~/upgrade-bookwormstep.script
That command is already using Bourne family shell synta
On Wed, Feb 14, 2024 at 05:35:59PM +0100, Franco Martelli wrote:
> On 14/02/24 at 17:15, Greg Wooledge wrote:
> > > # env LC_ALL=C script -t 2>~/upgrade-bookwormstep.time -a
> > > ~/upgrade-bookwormstep.script
> > That command is already using Bourne family shell syntax (the 2> part)
> > so you can
On Wed, Feb 14, 2024 at 05:11:55PM +0100, Franco Martelli wrote:
> Well, I'll go with env command syntax for shells portability. I was asking
> this because I want to suggest a change to the DDP (Debian Documentation
> Project) members for the releases notes documentation ¹
>
&g
t I posted, env will
also require an exec() and probably some dynamic linking.
Well, I'll go with env command syntax for shells portability. I was
asking this because I want to suggest a change to the DDP (Debian
Documentation Project) members for the releases notes documentation ¹
The ch
On 2/13/24 22:11, Greg Wooledge wrote:
On Tue, Feb 13, 2024 at 09:47:52PM -0500, Gremlin wrote:
This is from a script installed by a package that does a
dpkg-reconfigure locales to set the locale on the machine.
What package? What script?
I am working on it with a high rate a speed, should
On Tue, Feb 13, 2024 at 09:47:52PM -0500, Gremlin wrote:
> This is from a script installed by a package that does a
> dpkg-reconfigure locales to set the locale on the machine.
What package? What script?
> BTW where is LANGUAGE defined in the "standards/conventions"?
It's a GNUism.
https://www
On 2/13/24 21:22, Max Nikulin wrote:
On 14/02/2024 07:56, Gremlin wrote:
Gremlin (12024-02-13):
cat /etc/default/locale
# File generated by update-locale
LANG=en_US.UTF-8
LANGUAGE=en_US.UTF-8
Found this in a shell script:
LC_ALL=$LOC LANG=$LOC LANGUAGE=$LOC update-locale LANG=$LOC
LC_ALL=
On 14/02/2024 07:56, Gremlin wrote:
Gremlin (12024-02-13):
cat /etc/default/locale
# File generated by update-locale
LANG=en_US.UTF-8
LANGUAGE=en_US.UTF-8
Found this in a shell script:
LC_ALL=$LOC LANG=$LOC LANGUAGE=$LOC update-locale LANG=$LOC LC_ALL=$LOC
LANGUAGE=$LOC
Do not do it for
On Tue, Feb 13, 2024 at 07:56:46PM -0500, Gremlin wrote:
> Found this in a shell script:
>
> LC_ALL=$LOC LANG=$LOC LANGUAGE=$LOC update-locale LANG=$LOC LC_ALL=$LOC
> LANGUAGE=$LOC
In *what* shell script?
On 2/13/24 19:29, Gremlin wrote:
On 2/13/24 17:48, Nicolas George wrote:
Gremlin (12024-02-13):
Oh like debian does?
cat /etc/default/locale
# File generated by update-locale
LANG=en_US.UTF-8
LANGUAGE=en_US.UTF-8
LC_ALL=en_US.UTF-8
I do not observe this, even after “sudo dpkg-reconfigure lo
Hi,
On Tue, Feb 13, 2024 at 07:29:37PM -0500, Gremlin wrote:
> Upon investigation, I can not determine which package
> /etc/default/locale belongs too.
dpkg -S and apt-file will only find files that are actually shipped
in packages. Files that are created or used by maintainer scripts
but not act
On 2/13/24 17:48, Nicolas George wrote:
Gremlin (12024-02-13):
Oh like debian does?
cat /etc/default/locale
# File generated by update-locale
LANG=en_US.UTF-8
LANGUAGE=en_US.UTF-8
LC_ALL=en_US.UTF-8
I do not observe this, even after “sudo dpkg-reconfigure locales”. Can
you explain how you re
On Tue, Feb 13, 2024 at 11:48:04PM +0100, Nicolas George wrote:
> Gremlin (12024-02-13):
> > Oh like debian does?
> >
> > cat /etc/default/locale
> > # File generated by update-locale
> > LANG=en_US.UTF-8
> > LANGUAGE=en_US.UTF-8
> > LC_ALL=en_US.UTF-8
>
> I do not observe this, even after “sudo
Gremlin (12024-02-13):
> Oh like debian does?
>
> cat /etc/default/locale
> # File generated by update-locale
> LANG=en_US.UTF-8
> LANGUAGE=en_US.UTF-8
> LC_ALL=en_US.UTF-8
I do not observe this, even after “sudo dpkg-reconfigure locales”. Can
you explain how you reached this state?
--
Nicol
On 2/13/24 16:45, Greg Wooledge wrote:
On Tue, Feb 13, 2024 at 01:21:20PM -0800, John Conover wrote:
egrep ALL .bashrc
LC_ALL=C
This has gone pretty far off the rails, but here we are. Let's address
this.
DO NOT set LC_ALL in your .bashrc or equivalent files. This is a horrible
id
Will Mengarini (12024-02-13):
> * Greg Wooledge [24-02/13=Tu 15:59 -0500]:
> > In csh, you need to use env. Like this:
> What Greg posted also works, because it's an
> invocation of the 'env' command, not csh syntax.
Yes. What made Greg's statement false was not the fact th
> On Tue, Feb 13, 2024 at 09:47:38PM +0100, Franco Martelli wrote:
>> ~# LC_ALL=C apt install
>> [... works on ...] all shells other than bash? csh, korn, dash, zsh ...
* Greg Wooledge [24-02/13=Tu 15:59 -0500]:
> [...] all the Bourne family shells [...]
>
> In csh, yo
On Tue, Feb 13, 2024 at 01:21:20PM -0800, John Conover wrote:
> egrep ALL .bashrc
> LC_ALL=C
This has gone pretty far off the rails, but here we are. Let's address
this.
DO NOT set LC_ALL in your .bashrc or equivalent files. This is a horrible
idea. LC_ALL should only be used in single
John Conover (12024-02-13):
> > variable LC_ALL to "C" inline of the command e.g.:
^
> egrep ALL .bashrc
> LC_ALL=C
>
> set | egrep ALL
> LC_ALL=C
>
> dash
> set | egrep ALL
You missed part of the question, what you are showi
Franco Martelli writes:
>
> If I want English output of an application I set the environment
> variable LC_ALL to "C" inline of the command e.g.:
>
.
.
.
>
> So the question is: does anybody know if this syntax works on all shells
> other than bash? csh, ko
Greg Wooledge (12024-02-13):
> This syntax works in all the Bourne family shells, which is all of the
> above *except* csh.
>
> In csh, you need to use env.
No, ( setenv var something ; command ) works with csh.
> % env LC_ALL=C apt install
>
> This works in all s
On Tue, Feb 13, 2024 at 09:47:38PM +0100, Franco Martelli wrote:
> ~# LC_ALL=C apt install
> So the question is: does anybody know if this syntax works on all shells
> other than bash? csh, korn, dash, zsh …
This syntax works in all the Bourne family shells, which is all of the
abov
s anybody know if this syntax works on all shells
> other than bash? csh, korn, dash, zsh …
apt-get install csh
csh
LC_CTYPE=C ls /doesnotexist
^D
apt-get purge csh
Repeat with other shells. And then tell us what you found out.
Regards,
--
Nicolas George
This is useful when it's needed to submit a bug report or to speak with
other people in one international mailing list like this :) (apropos
sorry for my English).
So the question is: does anybody know if this syntax works on all shells
other than bash? csh, korn, dash, zsh …
Tha
On Fri, May 20, 2022 at 09:36:40PM -0400, The Wanderer wrote:
> I wasn't even thinking of it in those terms, although now that you point
> it out that's a good thing to be aware of. I was thinking of it in terms
> of A: trying to write scripts that are safe against such problematic
> elements being
On 2022-05-20 at 21:20, Greg Wooledge wrote:
> On Fri, May 20, 2022 at 08:41:43PM -0400, The Wanderer wrote:
>
>> On 2022-05-20 at 20:28, David Wright wrote:
>>
>> > $ function /usr/bin/sudo { echo teehee; }
>> > $ /usr/bin/sudo whatever
>> > teehee
>> > $
>>
>> A quick test demonstrates that th
On Fri, May 20, 2022 at 08:41:43PM -0400, The Wanderer wrote:
> On 2022-05-20 at 20:28, David Wright wrote:
> > $ function /usr/bin/sudo { echo teehee; }
> > $ /usr/bin/sudo whatever
> > teehee
> > $
>
> A quick test demonstrates that this can be worked around via the 'unset'
> command:
Until yo
On 2022-05-20 at 20:28, David Wright wrote:
> On Thu 19 May 2022 at 15:42:33 (-0500), Nicholas Geovanis wrote:
>
>> On Thu, May 19, 2022, 3:14 AM 황병희 wrote:
>> > Tom Browder writes:
>> >
>> > > I need a special path setting for root after both "sudo" and "sudo
>> > > su." (...)
>> >
>> > Just yo
On 20/10/2020 15:51, rhkra...@gmail.com wrote:
Top posting intentionally as I don't think any (or much) context is required.
so, hijacking a thread instead? :-)
--
Tony van der Hoff| mailto:t...@vanderhoff.org
Buckinghamshire, England |
rhkra...@gmail.com (12020-10-20):
> Top posting intentionally as I don't think any (or much) context is required.
Then you could just omit it.
> I am always impressed with Greg's knowledge of the Bash shell (maybe all
> shells), but, wow, Bash seems like a convoluted mess t
Top posting intentionally as I don't think any (or much) context is required.
I am always impressed with Greg's knowledge of the Bash shell (maybe all
shells), but, wow, Bash seems like a convoluted mess to keep track of all the
little details / gotchas.
Is there a shell that is bett
David Wright composed on 2020-09-15 21:38 (UTC-0500):
> I ought to have guessed—I don't know how you keep track of so many!
I have a spreadsheet for tracking several things, such as dates of last
update/upgrade, video card installed, which DE. Each disk's partition inventory
is
comprised mostly
On Tue 15 Sep 2020 at 14:42:11 (-0400), Felix Miata wrote:
> David Wright composed on 2020-09-15 12:32 (UTC-0400):
>
> > Felix's first post came from, I don't quite get.
>
> Fallible memory. I use multiple distros, and do a lot more upgrading than new
> installs. openSUSE, last I installed, a mon
David Wright composed on 2020-09-15 12:32 (UTC-0400):
> Felix's first post came from, I don't quite get.
Fallible memory. I use multiple distros, and do a lot more upgrading than new
installs. openSUSE, last I installed, a month ago, puts something on each of
tty1-12. 1 is the installer itself, i
On Tue 15 Sep 2020 at 04:39:49 (+1000), David wrote:
> On Tue, 15 Sep 2020 at 04:27, David wrote:
> > On Tue, 15 Sep 2020 at 00:10, David Wright wrote:
> > > On Mon 14 Sep 2020 at 19:48:37 (+1000), David wrote:
>
> > > > To explore and confirm and maybe learn something from
> > > > smarter peopl
On Tue, 15 Sep 2020 at 04:27, David wrote:
> On Tue, 15 Sep 2020 at 00:10, David Wright wrote:
> > On Mon 14 Sep 2020 at 19:48:37 (+1000), David wrote:
> > > To explore and confirm and maybe learn something from
> > > smarter people, I report below some actual test results:
[...]
Sorry for thi
using installer's interactive shells on
> > > > tty1-tty4?
> > To explore and confirm and maybe learn something from
> > smarter people, I report below some actual test results:
> > I begin by booting the buster installer on real hardware,
> > and it stop
Stefan Monnier composed on 2020-09-14 13:11 (UTC-0400):
> My recent experience is that I'm unable to predict which VC will be used
> for what any more (it used to be that the GUI sessions were in F7 and
> up, but nowadays it's usually F2 and up, tho on some of my machines it
> seems it's still F7
>> 1,3,4 are not available shells.
>> IIRC:
> That does not match my recent experience.
My recent experience is that I'm unable to predict which VC will be used
for what any more (it used to be that the GUI sessions were in F7 and
up, but nowadays it's usually F2
On Mon 14 Sep 2020 at 19:48:37 (+1000), David wrote:
> On Mon, 14 Sep 2020 at 04:05, Felix Miata wrote:
> > Richard Owlett composed on 2020-09-13 05:15 (UTC-0500):
>
> > > Where can I find description of using installer's interactive shells on
> > > tty1-t
On Mon, 14 Sep 2020 at 04:05, Felix Miata wrote:
> Richard Owlett composed on 2020-09-13 05:15 (UTC-0500):
> > Where can I find description of using installer's interactive shells on
> > tty1-tty4?
> 1,3,4 are not available shells.
> IIRC:
That does not match my rece
Richard Owlett composed on 2020-09-13 05:15 (UTC-0500):
> Where can I find description of using installer's interactive shells on
> tty1-tty4?
1,3,4 are not available shells.
IIRC:
tty1 is devoted to the installer
tty2 is an available shell
tty3 & 4 are devoted to various lo
On Sun 13 Sep 2020 at 05:15:38 (-0500), Richard Owlett wrote:
> Where can I find description of using installer's interactive shells
> on tty1-tty4?
>
> All I've found are passing mentions in
> https://www.debian.org/releases/stable/amd64/ch05s03.en.html
> htt
On 09/13/2020 05:45 AM, David wrote:
On Sun, 13 Sep 2020 at 20:16, Richard Owlett wrote:
Where can I find description of using installer's interactive shells on
tty1-tty4?
The installer is a running Linux system. What you ask about is a
standard feature that is compiled into most
On Sun, 13 Sep 2020 at 20:16, Richard Owlett wrote:
> Where can I find description of using installer's interactive shells on
> tty1-tty4?
The installer is a running Linux system. What you ask about is a
standard feature that is compiled into most Linux kernels, and the
feature exi
Richard Owlett writes:
Where can I find description of using installer's interactive shells on tty1-
tty4?
I am not sure how much documentation there is on it, but how about this
(section 6.3.9.2):
https://www.debian.org/releases/stable/amd64/ch06s03.en.html#di-miscellaneous
HTH
Linux-Fan
[...]
Where can I find description of using installer's interactive shells on
tty1-tty4?
All I've found are passing mentions in
https://www.debian.org/releases/stable/amd64/ch05s03.en.html
https://www.debian.org/releases/stable/amd64/ch06s03.en.html
On Thu, Jun 09, 2016 at 11:22:32PM -0700, Marc Shapiro wrote:
> On 06/09/2016 10:00 AM, Levi Darrell wrote:
> >Hi Debian Users List,
> >
> >My computer is set to boot into a tty shell. I manually enter X Server by
> >issuing the startx command. Previously, I had been a
On 06/09/2016 10:00 AM, Levi Darrell wrote:
Hi Debian Users List,
My computer is set to boot into a tty shell. I manually enter X Server
by issuing the startx command. Previously, I had been able to switch
tty shells with the keystroke combination Alt + F[1-6]. After
attempting to
Hi Debian Users List,
My computer is set to boot into a tty shell. I manually enter X Server by
issuing the startx command. Previously, I had been able to switch tty
shells with the keystroke combination Alt + F[1-6]. After attempting to
reconfigure they keyboard and locales to solve an unrelated
s /usr/bin/zsh) and when I typed whereis zsh it
>only returned:
>
># whereis zsh
>zsh:
>#
>
>I notice now that /etc/shells lists two Z shells;
>
>/bin/zsh
>/usr/bin/zsh
>
>I was wondering why this might be?
>
>Thanks,
>
>J
>
If a user has a login
John Aten writes:
> I notice now that /etc/shells lists two Z shells;
>
> /bin/zsh
> /usr/bin/zsh
>
> I was wondering why this might be?
On my system, both of those are symlinks that eventually lead to the
/bin/zsh4 binary (via symlinks in /etc/alternatives/).
Alexis.
zsh
zsh:
#
I notice now that /etc/shells lists two Z shells;
/bin/zsh
/usr/bin/zsh
I was wondering why this might be?
Thanks,
J
-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
Comment: GPGTools - https://gpgtools.org
iQEcBAEBCgAGBQJUL04gAAoJED6rE5ImPwfDULMH
On 9/1/13, Claudius Hubig wrote:
> Dear Zenaan,
>
> Zenaan Harkness wrote:
>> >From an existing plain xterm, I want this command:
>> uxterm -e /bin/bash -c /usr/bin/screen
>>
>> or eg:
>> uxterm -e /bin/bash -c /bin/sh
>>
>> To result in a nested shell. Basically I want my xterms to open by
>> def
Dear Zenaan,
Zenaan Harkness wrote:
> >From an existing plain xterm, I want this command:
> uxterm -e /bin/bash -c /usr/bin/screen
>
> or eg:
> uxterm -e /bin/bash -c /bin/sh
>
> To result in a nested shell. Basically I want my xterms to open by
> default with a screen session (which works fine)
>From an existing plain xterm, I want this command:
uxterm -e /bin/bash -c /usr/bin/screen
or eg:
uxterm -e /bin/bash -c /bin/sh
To result in a nested shell. Basically I want my xterms to open by
default with a screen session (which works fine), but I want to be
able to log out of screen with CTR
On Tue, Nov 27, 2012 at 10:37:09PM +0100, berenger.mo...@neutralite.org wrote:
> informations. With apt-cache if I am running my debian, or with
> http://packages.debian.org/search?keywords=foobar if I am not using
A shortcut for this is http://packages.debian.org/
Cheers,
Tom
--
The flow char
On Tue, 2012-11-27 at 22:37 +0100, berenger.mo...@neutralite.org wrote:
> >
> > I tried google, but without more keywords, "rc" was too little to
> > search.
>
> When I search for a package's description, I first use debian's
> informations. With apt-cache if I am running my debian, or with
> h
On Tue, Nov 27, 2012 at 03:43:00PM -0300, Beco wrote:
> I tried google, but without more keywords, "rc" was too little to search.
Good point, sorry.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Ar
I tried google, but without more keywords, "rc" was too little to
search.
When I search for a package's description, I first use debian's
informations. With apt-cache if I am running my debian, or with
http://packages.debian.org/search?keywords=foobar if I am not using it.
The 2nd is really
n the AT&T Plan 9 shell of the same name. The shell offers a C-like
syntax (much more so than the C shell), and a powerful mechanism for
manipulating variables. It is reasonably small and reasonably fast, especially
when compared to contemporary shells. Its use is intended to be interactive,
On Tue, Nov 27, 2012 at 7:17 AM, Beco wrote:
> On Tue, Nov 27, 2012 at 9:03 AM, Jon Dowland wrote:
>> On Tue, Nov 27, 2012 at 12:53:30PM +0100, "Morel Bérenger" wrote:
>>> People can use other things than bash, I do not see the problem. And I
>>> think that someday I'll try zsh or csh. When I'll
On Tue, Nov 27, 2012 at 12:17:50PM -0300, Beco wrote:
> Never heard of it. What is "rc"?
A shell. It's packaged in Debian, oddly enough in package 'rc'.
May I suggest you try "apt-cache show rc", or google?
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "uns
On Tue, Nov 27, 2012 at 9:03 AM, Jon Dowland wrote:
> On Tue, Nov 27, 2012 at 12:53:30PM +0100, "Morel Bérenger" wrote:
>> People can use other things than bash, I do not see the problem. And I
>> think that someday I'll try zsh or csh. When I'll have the time :D
>
> You should go really left-fiel
On Tue, Nov 27, 2012 at 12:53:30PM +0100, "Morel Bérenger" wrote:
> People can use other things than bash, I do not see the problem. And I
> think that someday I'll try zsh or csh. When I'll have the time :D
You should go really left-field and try rc! (but not for /bin/sh.)
--
To UNSUBSCRIBE, e
the tty.
So i exited shell 7 (ssh) and tried to ssh into my Debian box and it did.
What's up? I can't ssh through the other shells.
Cheers
Mark
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@list
On Fri, 9 Nov 2007 07:55:30 -0800
Andrew Sackville-West <[EMAIL PROTECTED]> wrote:
Hello Andrew et al,
> I, for one, welcome our dupe erasing overlords.
Another option, for the unaware, is to ignorespace (in fact, there's
also ignoreboth), which will not add to the bash history file anything
pre
On Fri, Nov 09, 2007 at 07:01:38AM -0600, Ron Johnson wrote:
>
> Tremble with fear puny humans, and welcome your bash overlord.
I, for one, welcome our dupe erasing overlords.
A
signature.asc
Description: Digital signature
them several
>>> times. Can the shell be more smart?
>>
>> Put in ~/.bashrc
>>
>> export HISTCONTROL=ignoredups
>
>
> Here I go and mention all these neat opportunities to try out other
> shells, and bash already has the feature that was requested. Darn
On Tue, May 15, 2007 at 01:10:41AM EDT, Alex Samad wrote:
> what about something like this
>
>
> NL='
> '
> IFS=$NL
> set -- $(find "$IND" -regextype posix-egrep -type f -iregex
> ".*\.(ogg)"
> -printf "%P\n")
> unset IFS
>
>
;
> Further processing would then need be done on the string to break it up
> into pieces, or not, as dictated by the needs of the caller. My 'child
> | read a b c d' is a quick way to read in the multiple lines output by
> your method, or to break a long line up on any w
s output by
> your method, or to break a long line up on any white space characters.
> Without using the arrays suggested by another poster, which may not be
> supported by all versions of Bourne type shells.
I was vaguely hoping bash's arrays might be passed to the child via a
pointer
. My 'child
| read a b c d' is a quick way to read in the multiple lines output by
your method, or to break a long line up on any white space characters.
Without using the arrays suggested by another poster, which may not be
supported by all versions of Bourne type shells.
Bob
;
> >cz=($(child)) /* note added outer parentheses .. */
> >
> >$p0="${cz[0]}"
> >$p1="${cz[1]}"
> >$p2="${cz[1]}"
> >
> >..
> >
> >I think you need a fairly recent version of bash to do this .. D
.*/
echo "[EMAIL PROTECTED]"
. parent:
cz=($(child)) /* note added outer parentheses .. */
$p0="${cz[0]}"
$p1="${cz[1]}"
$p2="${cz[1]}"
..
I think you need a fairly recent version of bash to do this .. Dunno
about
c4 .. etc.*/
echo "[EMAIL PROTECTED]"
. parent:
cz=($(child)) /* note added outer parentheses .. */
$p0="${cz[0]}"
$p1="${cz[1]}"
$p2="${cz[1]}"
..
I think you need a fairly recent version of bash to do this .. Dunno
about other
On Fri, May 11, 2007 at 08:53:18AM -0500, Ron Johnson wrote:
>
> On 05/11/07 08:24, Jan-Florian Hilgenberg wrote:
> > Hi guy's, first I am german, so ignore my bad english please ;-)
> >
> > i want to get a variable out of a child shell in it parent shell, the sense
> > is, that I want to use the
On Fri, May 11, 2007 at 08:53:18AM -0500, Ron Johnson wrote:
> On 05/11/07 08:24, Jan-Florian Hilgenberg wrote:
> > Hi guy's, first I am german, so ignore my bad english please ;-)
> >
> > i want to get a variable out of a child shell in it parent shell, the sense
> > is, that I want to use the Pr
On Fri, May 11, 2007 at 03:35:30PM +0100, Karl E. Jorgensen wrote:
> On Fri, May 11, 2007 at 03:24:46PM +0200, Jan-Florian Hilgenberg wrote:
>
> > But i wish that my System get a IP for ethernet on every bootup, I know
> > there is the option to put a process in the background by "command &", wher
Jan-Florian Hilgenberg wrote:
Hi guy's, first I am german, so ignore my bad english please ;-)
i want to get a variable out of a child shell in it parent shell, the
sense is, that I want to use the ProxyServer of my school automaticly if
it is pingable, the script isn't hard but the variable i
up in the
> /etc/network/interfaces.
You could try adding the environment variable to /etc/environment (or
removing it, if appropriate). Then at least the environment variable
would be available to new login shells.
> And because it was so fair, i explain you an other problem.
> I have disab
On Fri, May 11, 2007 at 03:24:46PM +0200, Jan-Florian Hilgenberg wrote:
> Hi guy's, first I am german, so ignore my bad english please ;-)
Kein problem. (or is it "Keine problem"? feminimum for "problem" is so
much more appropriate than neutrum/maskulinum...)
> i want to get a variable out of a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/11/07 08:24, Jan-Florian Hilgenberg wrote:
> Hi guy's, first I am german, so ignore my bad english please ;-)
>
> i want to get a variable out of a child shell in it parent shell, the sense
> is, that I want to use the ProxyServer of my school a
Hi guy's, first I am german, so ignore my bad english please ;-)
i want to get a variable out of a child shell in it parent shell, the sense
is, that I want to use the ProxyServer of my school automaticly if it is
pingable, the script isn't hard but the variable isn't fully global after
exporting
On Mon, Dec 18, 2006 at 11:19:00PM -0600, W Paul Mills wrote:
> > /etc/shells? Most notably, are there any security considerations?
> >
> > I wish to create a user that can log in to my FTP server, but without
> > shell access. I can prevent the shell access by specifyi
> On Mon, Dec 18, 2006 at 03:49:26PM +0100, L.W. van Braam van Vloten wrote:
> > Is there any objection against adding /bin/false to the file
> > /etc/shells? Most notably, are there any security considerations?
> >
> > I wish to create a user that can log in to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
L.W. van Braam van Vloten wrote:
> Hello group,
>
> Is there any objection against adding /bin/false to the file
> /etc/shells? Most notably, are there any security considerations?
>
> I wish to create a user that can log in to
1 - 100 of 188 matches
Mail list logo
