stupid question on vi

2025-02-22 Thread Dave Tyson
Apologies for being thick, but I struggling with a really simple problem. I have a file which has some hex characters 0x80 and higher. I am trying to search for them so I can replace them. I can see them and they appear, for example, like \x93 on the screen and occupy a single character. I have t

Re: Slow SSD disk

2025-02-22 Thread RVP
On Fri, 21 Feb 2025, Peter Skvarka wrote: [ 1.011893] pciide0 at pci0 dev 31 function 2: Intel 7 Series (desktop) SATA Controller (rev. 0x04) [ 1.011893] pciide0: bus-master DMA support present, but unused (no driver support) [ 1.011893] pciide0: primary channel configured to nativ

Re: stupid question on vi

2025-02-22 Thread Robert Elz
Date:Sat, 22 Feb 2025 23:08:42 + From:Dave Tyson Message-ID: <0a81f160c933bb8f824b03cbeb87305dfa8262da.ca...@anduin.org.uk> | I am trying to search for them so I can replace them. You need to type a literal 0x93 character and search for that. It shouldn't need

Re: stupid question on vi

2025-02-22 Thread Van Ly
Dave Tyson writes: > > I have used sed to do do replacements fine, but I just want to locate > some errant characters so I can see the context. > Two thing you can try on Grok 3: — tell Grok to write a Perl script to your requirements — upload your file to Grok and request what you are after

Re: stupid question on vi

2025-02-22 Thread RVP
On Sat, 22 Feb 2025, Dave Tyson wrote: I have a file which has some hex characters 0x80 and higher. I am trying to search for them so I can replace them. I can see them and they appear, for example, like \x93 on the screen and occupy a single character. nvi(1) has a poorly-documented Ctrl-X