Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #264654
| From | songbird <songbird@anthive.com> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: Image handling in mutt |
| Date | 2023-12-11 21:20 +0100 |
| Message-ID | <HJUUV-cUlY-1@gated-at.bofh.it> (permalink) |
| References | (7 earlier) <HJuQN-cEeZ-3@gated-at.bofh.it> <HJwSC-cFoT-1@gated-at.bofh.it> <HJx2h-cFsl-1@gated-at.bofh.it> <HJDhn-cJg3-1@gated-at.bofh.it> <HJQoh-cRBs-9@gated-at.bofh.it> |
| Organization | the little wild kingdom |
debian-user@howorth.org.uk wrote: > songbird <songbird@anthive.com> wrote: >> <tomas@tuxteam.de> wrote: >> > On Sun, Dec 10, 2023 at 01:28:20PM -0500, songbird wrote: >> >> <tomas@tuxteam.de> wrote: >> >> there is rarely a need to e-mail me directly. >> >> >> ... >> >> > That's why I cringe when people name executables "foo.sh". What >> >> > do you do when you decide to rewrite the thing in C (or Rust, or >> >> > whatever)? >> >> > >> >> > Do you go over all calling sites and change the caller's code? >> >> >> >> no, i would just consider it a transition or a change >> >> in versions. :) >> > >> > Again. You have one script, say /usr/local/bin/ring-the-bells.sh >> > You use it in several other scripts. If you now re-implement it >> > in your favourite Pascal as ring-the-bells.pas or something, you >> > go over all your executables and fix that? >> > >> > IMO an executable name should indicate /what/ an executable does, >> > not /how/. >> >> i'm fine with that, but i'm also capable enough to know >> how to search through a code base to find all the strings >> i might need to change. > > You make the anti-heroic assumption that your code is never used > outside of your control (or specifically, outside of your code base). if someone else uses it then they can do what they want with it. i can only control my own local system and that is all i am concerned about. in actual programming with libraries there are these things called APIs and ABIs and both are usually documented and defined if it is important enough and used enough. IMO most of my code does not reach that level of use. >> i just scanned a few of my projects and noted i do not >> use the .sh extension much at all for the binaries/executables, >> but parts of the code may have that extension. > > That's a fine choice, as long as none of the internals will be exposed > externally, IMHO. Though I confess I do often add a .pl extension to > filenames :( not something i'm worried about for sure. > PS I suspect tomas sent mail to you for the same reason I nearly did, > namely that you or your mailer explicitly asked for it with a reply-to > header. Certainly my claws MUA interprets that as meaning you want a > copy too. correct, so if you are going to reply to me personally that is the right address to use, but since i interact with this list via gmane and usenet a followup to me should go to the list and not to me personally. i would assume that group reply is one that everyone should be using automatically for mail list participation using a mail client unless the person mentions they are not subscribed and would like personal replies. songbird
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Image handling in mutt Paul M Foster <paulf@quillandmouse.com> - 2023-12-08 18:00 +0100
Re: Image handling in mutt David Wright <deblis@lionunicorn.co.uk> - 2023-12-08 18:10 +0100
Re: Image handling in mutt Paul M Foster <paulf@quillandmouse.com> - 2023-12-08 22:50 +0100
Re: Image handling in mutt David <bouncingcats@gmail.com> - 2023-12-08 23:00 +0100
Re: Image handling in mutt Pocket <pocket@columbus.rr.com> - 2023-12-08 23:10 +0100
Re: Image handling in mutt Greg Wooledge <greg@wooledge.org> - 2023-12-08 23:40 +0100
Re: Image handling in mutt Pocket <pocket@columbus.rr.com> - 2023-12-08 23:50 +0100
Re: Image handling in mutt Greg Wooledge <greg@wooledge.org> - 2023-12-09 00:00 +0100
Re: Image handling in mutt Pocket <pocket@columbus.rr.com> - 2023-12-09 00:10 +0100
Re: Image handling in mutt Greg Wooledge <greg@wooledge.org> - 2023-12-09 00:20 +0100
Re: Image handling in mutt Pocket <pocket@columbus.rr.com> - 2023-12-09 00:30 +0100
Re: Image handling in mutt Pocket <pocket@columbus.rr.com> - 2023-12-09 00:00 +0100
Re: Image handling in mutt John Hasler <john@sugarbit.com> - 2023-12-09 00:00 +0100
Re: Image handling in mutt Greg Wooledge <greg@wooledge.org> - 2023-12-09 00:00 +0100
Re: Image handling in mutt Pocket <pocket@columbus.rr.com> - 2023-12-09 00:30 +0100
Re: Image handling in mutt Eric S Fraga <e.fraga@ucl.ac.uk> - 2023-12-09 09:50 +0100
Re: Image handling in mutt Curt <curty@free.fr> - 2023-12-10 17:20 +0100
Re: Image handling in mutt <tomas@tuxteam.de> - 2023-12-10 17:30 +0100
Re: Image handling in mutt songbird <songbird@anthive.com> - 2023-12-10 19:40 +0100
Re: Image handling in mutt <tomas@tuxteam.de> - 2023-12-10 19:50 +0100
Re: Image handling in mutt David Wright <deblis@lionunicorn.co.uk> - 2023-12-10 21:20 +0100
Re: Image handling in mutt songbird <songbird@anthive.com> - 2023-12-11 02:30 +0100
Re: Image handling in mutt debian-user@howorth.org.uk - 2023-12-11 16:30 +0100
Re: Image handling in mutt songbird <songbird@anthive.com> - 2023-12-11 21:20 +0100
Re: Image handling in mutt Vincent Lefevre <vincent@vinc17.net> - 2023-12-11 12:40 +0100
Re: Image handling in mutt Pocket <pocket@columbus.rr.com> - 2023-12-11 13:30 +0100
Re: Image handling in mutt "Loris Bennett" <loris.bennett@fu-berlin.de> - 2023-12-11 14:10 +0100
Re: Image handling in mutt David Wright <deblis@lionunicorn.co.uk> - 2023-12-10 21:10 +0100
Re: Image handling in mutt Pocket <pocket@columbus.rr.com> - 2023-12-10 22:00 +0100
Re: Image handling in mutt Vincent Lefevre <vincent@vinc17.net> - 2023-12-11 13:20 +0100
Re: Image handling in mutt Pocket <pocket@columbus.rr.com> - 2023-12-11 13:40 +0100
Re: Image handling in mutt Arno Lehmann <al@its-lehmann.de> - 2023-12-11 13:50 +0100
Re: Image handling in mutt Greg Wooledge <greg@wooledge.org> - 2023-12-11 14:20 +0100
Re: Image handling in mutt Vincent Lefevre <vincent@vinc17.net> - 2023-12-11 15:10 +0100
Re: Image handling in mutt Pocket <pocket@columbus.rr.com> - 2023-12-11 15:40 +0100
Re: Image handling in mutt Vincent Lefevre <vincent@vinc17.net> - 2023-12-11 16:20 +0100
Re: Image handling in mutt "Jeremy Nicoll" <jn.ml.dbi.73@letterboxes.org> - 2023-12-11 19:00 +0100
Re: Image handling in mutt jeremy ardley <jeremy.ardley@gmail.com> - 2023-12-11 23:10 +0100
On file systems [was: Image handling in mutt] <tomas@tuxteam.de> - 2023-12-12 06:40 +0100
Re: On file systems "Thomas Schmitt" <scdbackup@gmx.net> - 2023-12-12 11:50 +0100
Re: Image handling in mutt Eric S Fraga <e.fraga@ucl.ac.uk> - 2023-12-11 13:50 +0100
Re: Image handling in mutt Vincent Lefevre <vincent@vinc17.net> - 2023-12-11 15:00 +0100
Re: Image handling in mutt <tomas@tuxteam.de> - 2023-12-11 15:20 +0100
Re: Image handling in mutt Vincent Lefevre <vincent@vinc17.net> - 2023-12-11 15:40 +0100
Re: Image handling in mutt <tomas@tuxteam.de> - 2023-12-11 15:50 +0100
Re: Image handling in mutt Pocket <pocket@columbus.rr.com> - 2023-12-11 15:50 +0100
Re: Image handling in mutt David Wright <deblis@lionunicorn.co.uk> - 2023-12-11 16:00 +0100
Re: Image handling in mutt Pocket <pocket@columbus.rr.com> - 2023-12-11 16:10 +0100
Re: Image handling in mutt David Wright <deblis@lionunicorn.co.uk> - 2023-12-11 17:10 +0100
Re: Image handling in mutt <tomas@tuxteam.de> - 2023-12-11 16:10 +0100
Re: Image handling in mutt Stefan Monnier <monnier@iro.umontreal.ca> - 2023-12-11 16:20 +0100
Re: Image handling in mutt <tomas@tuxteam.de> - 2023-12-11 16:30 +0100
Re: Image handling in mutt Zenaan Harkness <zenaan@gmail.com> - 2023-12-11 00:10 +0100
Re: Image handling in mutt Zenaan Harkness <zenaan@gmail.com> - 2023-12-11 01:20 +0100
Re: Image handling in mutt David Wright <deblis@lionunicorn.co.uk> - 2023-12-11 16:30 +0100
csiph-web