Hello,
Le ven. 27 mai 2022 à 20:45, Greg Reagle a écrit :
>
> I have a file named "out" (from ii) that I want to view. Of course, it can
> grow while I am viewing it. I can view it with "tail -f out" or "less +F
> out", both of which work. I also want to apply some processing in a
> pipelin
ntf's to be
exploded into several puts, though.
Not sure about all my choices; criticism is welcome.
Cheers
-- AN
>From 02a5919fa0895f694eb8f2b94c387cf21601746b Mon Sep 17 00:00:00 2001
From: Alexandre Niveau
Date: Thu, 14 May 2015 23:37:54 +0200
Subject: [PATCH 1/2] ls: fix opt
There's a problem in isprintrune in sbase, it can only return 0 because
of the “&& (r < 0xFFF9) && (r > 0xFFFB)” part. When fixing it (and the
others problems I mentioned earlier), Ralph's patch works (it needs
cleaning though).
The only real way to do this is to also look at wide characters.
ls -q replaces non printable characters with '?'; I'm not sure how to
make files with non-printable characters as yet,
touch "$(printf 'foo\nbar')"
touch "this $(tput setaf 1) is red"
You can also use Control+V to enter the next character literally (tab,
CR, backspace, etc.).
all I know is
On 31/10/2014 20:45, FRIGN wrote:
Yeah, but I want the XML parser.
I supposed so, but since you referred to (X)HTML, I was unsure.
I'd say it's hard to suck less than that as far as HTML goes...
Well, look at what XHTML 2.0 tried to achieve (it was a step in the
right direction). I'll never
On 31/10/2014 16:48, FRIGN wrote:
To put it simply, what has the W3C been doing all these past years?
Right! Stacking more and more stuff on top of what was there. However,
writing (X)HTML hasn't become simpler in any way!
Or who can possibly remember this every time he writes a new page:
http
Hi,
On 04/08/2014 06:44, Michael Reed wrote:
Stty shows that iutf8 is enabled for me. I saw earlier in the thread you
verified your LC_ALL as being UTF-8, perhaps that or LANG is configured
on your filesystem but is not propogating to st due to some shell
configuration issue?
I'm not sure that
Hi,
On 24/07/2014 23:52, Roberto E. Vargas Caballero wrote:
Well, let me think. You press Backspace key (which generates ^H), and your
configuration of stty says that erase is ^H, but then it seems that it is
deleted only the last byte of the previous utf8 rune. This action is
performed by the k
2014-07-25 9:34 GMT+02:00 Roberto E. Vargas Caballero :
> [snip]
> The kernel has a line driver, which operates in different modes. When
> you are working in ed, the kernel reads all the characthers and
> allows line editing and only sends the characters to the user after
> a newline.
> [snip]
Tha
> In fact, in all the other systems backspace works as Delete. Delete
> is 7FH, or ^?, and backspace is 08H, or ^H. The point here is that, by
> default, linux assumes that your key for removing previous character
> is (erase key) is delete, that is remapped into the position of
> backspace. I had
Hi,
>> I have the same issue in mg. This question also comes up occasionally
>> on IRC. Reverting the commit you specified seems to work for mg (but
>> may break other applications?) Can anyone shed a light on it, for
>> science?
>
> This patch only changes the keystroke generated by Backspace (in
Hello,
I've been using st for a while now; it works great. Thanks to the devs
and maintainers!
I have a problem though, when using ed; I don't know whether it's a
bug in st or elsewhere. When typing a line in ed, using backspace to
erase a multibyte UTF-8 character *seems* OK visually, but does
12 matches
Mail list logo
