On Lu, 26 apr 21, 22:16:34, Cmdte Alpha Tigre Z wrote:
> Hi.
>
> I saw at the Debian Lists' archive
> that my attached files were not
> shown as attached (as in the
> BTS archive), but instead as inserted
> into the body of the message.
This is just how the archive software shows them, they arriv
On Lu, 26 apr 21, 20:34:58, Cmdte Alpha Tigre Z wrote:
>
> It would be great if someone could repost this tutorial at the Debian
> Wiki.
Feel free to do so yourself.
Kind regards,
Andrei
--
http://wiki.debian.org/FAQsFromDebianUser
signature.asc
Description: PGP signature
davidson wrote:
> >
> > I actually looked with `hd` and expected to see 0x20 there, but
> > somehow see none of it:
> >
> > $ echo $COMP_WORDBREAKS | hd
> > 22 27 40 3e 3c 3d 3b 7c 26 28 3a 0a |"'@><=;|&(:.|
> > 000c
>
> Above I count 12 characters piped from echo to
Hi.
I saw at the Debian Lists' archive
that my attached files were not
shown as attached (as in the
BTS archive), but instead as inserted
into the body of the message.
Is there some other way to attach
the files correctly?
Would it work and could I send the
attachments with HTML?
Well, thanks in
On the 25th of March of 2021, I wrote a message asking for help
to install Debian 10.8 (now 10.9) on a USB stick, booting the Debian-installer
from Windows 7's Boot Manager and having the ISO only on the hard disk drive
with only the Windows' partition and its filesystem.
Many thanks in advance to
El jue, 25 mar 2021 a las 21:11, Cmdte Alpha Tigre Z
() escribió:
> (...lots of things...)
Hi.
I'm going to post a tutorial to do what I did to achieve the
installation of Debian
in the USB stick from Windows' NTFS-formatted partition.
Please, review it and give your opinions/suggestions/fixes.
On 2021-04-26 02:43 PM, Steve Dondley wrote:
I downloaded and ran this docker image: https://hub.docker.com/_/debian
It works, but typically when I hit the ctrl-p key at the bash prompt,
it acts like the up arrow key and shows the previous command.
However, I have to hit ctrl-p twice to show th
On Mon 26 Apr 2021 at 18:27:57 (+), davidson wrote:
> On Mon, 26 Apr 2021 davidson wrote:
>
> Two corrections to previous message.
> > % Proposal D
> >
> > $ cat ~/.inputrc # a literal Shift-TAB is inside the double quotes
> > " ": menu-complete
>
> 2. The '^[' above is an artifact of...
I downloaded and ran this docker image: https://hub.docker.com/_/debian
It works, but typically when I hit the ctrl-p key at the bash prompt, it
acts like the up arrow key and shows the previous command.
However, I have to hit ctrl-p twice to show the previous command and
twice each time to s
On Mon, 26 Apr 2021 davidson wrote:
Two corrections to previous message.
[dd]
% Proposal C
In that case, you could get all but the last argument completed like
so:
$ complete -A hostname -P '-h ' -S ' -s'
1. At the end of the line above, the command name is missing.
$ complete -A hostnam
On Mon, 26 Apr 2021 Victor Sudakov wrote:
davidson wrote:
On Sat, 24 Apr 2021 Victor Sudakov wrote:
David Wright wrote:
I have an example app which can be run only as "app3 -h test1 -s
foo" or "app3 -h test2 -s bar". So I decided to provide it with
a small manual completion for convenience.
On Mon, Apr 26, 2021 at 01:49:42PM +0200, Thomas Schmitt wrote:
> > $ string=' hithere '
> > [...]
> > $ printf '<%s> ' $string ; echo
> >
>
> As C programmer i am now tempted to scream.
> (This command should really not have the same name as printf(3).)
There are a few changes between
Hi,
Greg Wooledge wrote:
> Not the parser, technically. The correct term is word splitting.
Always good to know which part of the shell tries to bite me. :))
> $ string=' hithere '
> [...]
> $ printf '<%s> ' $string ; echo
>
As C programmer i am now tempted to scream.
(This command
On Mon, Apr 26, 2021 at 12:04:45PM +0200, Thomas Schmitt wrote:
> > what accounts for the three missing characters (namely SPACE, TAB,
> > and NEWLINE)?
>
> They get eaten by the shell parser if you do not use quotation marks:
>
> $ echo $COMP_WORDBREAKS | wc -c
> 11
> $ echo "$COMP_WORDBRE
Hi,
> what accounts for the three missing characters (namely SPACE, TAB,
> and NEWLINE)?
They get eaten by the shell parser if you do not use quotation marks:
$ echo $COMP_WORDBREAKS | wc -c
11
$ echo "$COMP_WORDBREAKS" | wc -c
14
So to see all characters (including the newline added by
On Mon, 26 Apr 2021 Victor Sudakov wrote:
davidson wrote:
On Sat, 24 Apr 2021 Victor Sudakov wrote:
[dd]
BTW on my current Debian system I don't see the space character in
$COMP_WORDBREAKS.
If you have xxd installed, what does xxd show you?
I actually looked with `hd` and expected to see
16 matches
Mail list logo
