Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Muttley@dastardlyhq.com Newsgroups: comp.unix.shell,comp.unix.programmer,comp.lang.misc Subject: Re: Python (was Re: I did not inhale) Date: Sun, 15 Sep 2024 09:06:51 -0000 (UTC) Organization: A noiseless patient Spider Lines: 21 Message-ID: References: <20240826083330.00004760@gmail.com> <20240826155113.000005ba@gmail.com> Injection-Date: Sun, 15 Sep 2024 11:06:51 +0200 (CEST) Injection-Info: dont-email.me; posting-host="f8ebf5a63a1bedc307b8d92a4242b224"; logging-data="2204152"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/LG29orLPMOvtnxtRzSE4F" Cancel-Lock: sha1:f8boidte6ogS/nw2hw5862dJZi8= Bytes: 2069 On Sat, 14 Sep 2024 22:25:53 -0000 (UTC) Lawrence D'Oliveiro boringly babbled: >On Sat, 14 Sep 2024 19:10:06 GMT, Scott Lurndal wrote: > >> $ man vim | grep -i binary >> >> -b Binary mode. A few options will be set that makes it >> possible to edit a binary or executable file. > >Wow, a special mode just to edit binary files, when Emacs can do it in >its regular mode. The 1980s phoned, they want their editor wars back. >It just sets a bunch of options to minimize the chance of screwing up >the file in ways you don’t want. Apart from that, it’s still editing >it as a text file. Any sane person uses a dedicated hex editor to edit binary files, not vim or emacs.