On Sat, 12 Oct 2024, 23:50 Saint Michael, wrote:
> From: Saint Michael
> Date: Sat, Oct 12, 2024 at 9:49 AM
> Subject: New feature
>
> The command printf needs a new flag, -e, that would mimic that way the
> same flag works with echo.
> …
> PROCEDURE_INFO=$(echo -e "${PROCEDURE_INFO}")
> this s
On Mon, Jan 04, 2021 at 10:44:40AM -0500, Saint Michael wrote:
> can you point me to your FAQ?
https://mywiki.wooledge.org/BashFAQ/045
can you point me to your FAQ?
On Mon, Jan 4, 2021 at 8:39 AM Greg Wooledge wrote:
> On Mon, Jan 04, 2021 at 08:26:59AM -0500, Saint Michael wrote:
> > In this case, how do I quickly increase the number stored in "foo"?
> > the file has 1 as content, and I have a new value to add to it
> quic
Le 04/01/2021 à 14:14, Greg Wooledge écrivait :
It should be noted that $(
var=$(ending the last line because it exactly a sub-shell shot syntax for
var=$(cat file). Sub-shell $(commands list) output is always trimmed.
--
Léa Gris
On Mon, Jan 04, 2021 at 08:26:59AM -0500, Saint Michael wrote:
> In this case, how do I quickly increase the number stored in "foo"?
> the file has 1 as content, and I have a new value to add to it quickly.
> Is there an atomic way to read,add, write a value to "foo"?
Nope!
It's almost like b
In this case, how do I quickly increase the number stored in "foo"?
the file has 1 as content, and I have a new value to add to it quickly.
Is there an atomic way to read,add, write a value to "foo"?
On Mon, Jan 4, 2021 at 8:15 AM Greg Wooledge wrote:
> On Fri, Jan 01, 2021 at 10:02:26PM +0
On Fri, Jan 01, 2021 at 10:02:26PM +0100, Ángel wrote:
> Yes. In fact, you can already do that using an interface exactly
> identical to file operations:
>
> # Store a string in shared memory with key 'foo'
> echo "Hello world" > foo
>
> # Read value of key foo
> var="$(
>
> You only need to us
On 2020-12-27 at 13:30 -0500, Saint Michael wrote:
> Yes, superglobal is great.
> Example, from the manual:
> " Shared Memory
> Shared memory allows one or more processes to communicate via memory
> that appears in all of their virtual address spaces. The pages of the
> virtual memory is referenced
I agree: python seem to be more apropriated language for complex operation.
Anyway, bash already offer a lot of features (like `coproc` and `read -t 0`)
usefull for IPC.
I wrote a little ``multiping`` bash script, as multithread demo, running many
parallels ping, reading all outputs and merging t
On 12/27/20 1:30 PM, Saint Michael wrote:
We could allow only strings or more complex objects, but using bash-language
only, an internal mechanism, and also we need to define a semaphore.
Is it doable?
Of course it's doable; all that takes is requirements, definition, and
implementation. The
On 27/12/2020 at 19:30, Saint Michael wrote:
Yes, superglobal is great.
Example, from the manual:
" Shared Memory
Shared memory allows one or more processes to communicate via memory that
appears in all of their virtual address spaces. The pages of the virtual
memory is referenced by page table e
Yes, superglobal is great.
Example, from the manual:
" Shared Memory
Shared memory allows one or more processes to communicate via memory that
appears in all of their virtual address spaces. The pages of the virtual
memory is referenced by page table entries in each of the sharing
processes' page t
On 12/27/20 12:38 PM, Saint Michael wrote:
Bash is very powerful for its ability to use all kinds of commands and pipe
information through them. But there is a single thing that is impossible to
achieve except using files on the hard drive or on /tmp. We need a new
declare -g (global) where a var
On 10/28/20 10:51 AM, Dr. Werner Fink wrote:
> On 2020/10/28 10:23:57 -0400, Chet Ramey wrote:
>> On 10/16/20 9:28 AM, Chet Ramey wrote:
>>> On 10/16/20 9:16 AM, Dr. Werner Fink wrote:
>>>
Also a warning hint in the manual page could
help users before enabling this feature :)
>>>
>>> I ag
On 2020/10/28 10:23:57 -0400, Chet Ramey wrote:
> On 10/16/20 9:28 AM, Chet Ramey wrote:
> > On 10/16/20 9:16 AM, Dr. Werner Fink wrote:
> >
> >> Also a warning hint in the manual page could
> >> help users before enabling this feature :)
> >
> > I agree, and the manual page in the release will r
On 10/16/20 9:28 AM, Chet Ramey wrote:
> On 10/16/20 9:16 AM, Dr. Werner Fink wrote:
>
>> Also a warning hint in the manual page could
>> help users before enabling this feature :)
>
> I agree, and the manual page in the release will reflect bracketed paste's
> default setting. However, readline
On Fri, Oct 16, 2020 at 09:28:26AM -0400, Chet Ramey wrote:
> On 10/16/20 9:16 AM, Dr. Werner Fink wrote:
>
> > Also a warning hint in the manual page could
> > help users before enabling this feature :)
>
> I agree, and the manual page in the release will reflect bracketed paste's
> default sett
On 10/16/20 9:16 AM, Dr. Werner Fink wrote:
> Also a warning hint in the manual page could
> help users before enabling this feature :)
I agree, and the manual page in the release will reflect bracketed paste's
default setting. However, readline doesn't try to enable bracketed paste if
tcgetattr
On 2020/10/16 09:03:53 -0400, Chet Ramey wrote:
> On 10/16/20 5:41 AM, Dr. Werner Fink wrote:
> > Hi,
> >
> > after build rc1 of bash 5.1 as well as readline-8.1 I've set up test
> > staging process. During build the package python-pexpect throws errors
> > in its test suite, e.g.
> >
> > [ 260
On 10/16/20 5:41 AM, Dr. Werner Fink wrote:
> Hi,
>
> after build rc1 of bash 5.1 as well as readline-8.1 I've set up test
> staging process. During build the package python-pexpect throws errors
> in its test suite, e.g.
>
> [ 260s] self = testMethod=test_async_replwrap_multiline>
> [ 260s]
> what about something like
>
> function __bash_completion_loader() {
> source "/etc/bash_completion.d/$1.sh" &>/dev/null
> return 127
> }
> complete -F __bash_completion_loader ''
>
> which will catch all programmable completions? Need change in bash.
> More info at https://bugzilla.redhat.c
21 matches
Mail list logo
