Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #264649
| Path | csiph.com!fu-berlin.de!bofh.it!news.nic.it!robomod |
|---|---|
| From | "Jeremy Nicoll" <jn.ml.dbi.73@letterboxes.org> |
| Newsgroups | linux.debian.user |
| Subject | Re: Image handling in mutt |
| Date | Mon, 11 Dec 2023 19:00:01 +0100 |
| Message-ID | <HJSJr-cSTr-17@gated-at.bofh.it> (permalink) |
| References | <HJyhH-cGns-3@gated-at.bofh.it> <HJz46-cGE3-17@gated-at.bofh.it> <HJNqp-cPQS-3@gated-at.bofh.it> <HJNJL-cPXK-9@gated-at.bofh.it> <HJNTr-cQ17-1@gated-at.bofh.it> <HJOmt-cQqs-11@gated-at.bofh.it> |
| X-Original-To | "ML - debian-user" <debian-user@lists.debian.org> |
| X-Mailbox-Line | From debian-user-request@lists.debian.org Mon Dec 11 17:50:44 2023 |
| Old-Return-Path | <jn.ml.dbi.73@letterboxes.org> |
| X-Amavis-Spam-Status | No, score=-7.557 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FOURLA=0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, LDO_WHITELIST=-5, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no |
| X-Policyd-Weight | NOT_IN_SBL_XBL_SPAMHAUS=-1.5 CL_IP_EQ_HELO_IP=-2 (check from: .letterboxes. - helo: .wout1-smtp.messagingengine. - helo-domain: .messagingengine.) FROM/MX_MATCHES_HELO(DOMAIN)=-2; rate: -5.5 |
| X-Me-Sender | <xms:10t3ZRxswSfsMc9iew2LyxBhNaJwyGc9_TG2WysjTIq-pmv3LoiMOrru> <xme:10t3ZRRMQu6hMfnlN8LyB88yvugLFmetR8etIefbdCI4Y5foh9KGCOgXBCaht1Q28 YpjMl449wFOCrGM> |
| X-Me-Proxy-Cause | gggruggvucftvghtrhhoucdtuddrgedvkedrudelvddguddtkecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefofgggkfgjfhffhffvufgtsehttdertderredtnecuhfhrohhmpedflfgv rhgvmhihucfpihgtohhllhdfuceojhhnrdhmlhdruggsihdrjeefsehlvghtthgvrhgsoh igvghsrdhorhhgqeenucggtffrrghtthgvrhhnpeevjeejteelleejheekudevffejudei teegieeikeeggeefgfeffeeuleetfeeiieenucevlhhushhtvghrufhiiigvpedtnecurf grrhgrmhepmhgrihhlfhhrohhmpehjnhdrmhhlrdgusghirdejfeeslhgvthhtvghrsgho gigvshdrohhrgh |
| X-Me-Proxy | <xmx:10t3ZbW0ZHSalOksZ9cxTGeb4J4zIt_YdwaJhs331omtnjyXdZacLQ> <xmx:10t3ZTj7-trBXVZnPF3WFOT6YXZlfxSemli1DYh2Uh9hyyFVIVa9bg> <xmx:10t3ZTALdR68B-gdeNCAfTNezvfKrtHTLGkR_ZzvTIO9biLmADmo9g> <xmx:2Et3ZWO-cNLh5jGdmgLUgSubsqVefb8K6jPoK3bu8LAEUdGuLs-RNQ> |
| Feedback-ID | i1ea9464b:Fastmail |
| X-Mailer | MessagingEngine.com Webmail Interface |
| User-Agent | Cyrus-JMAP/3.9.0-alpha0-1178-geeaf0069a7-fm-20231114.001-geeaf0069 |
| MIME-Version | 1.0 |
| Content-Type | text/plain |
| X-Mailing-List | <debian-user@lists.debian.org> archive/latest/806446 |
| List-ID | <debian-user.lists.debian.org> |
| List-URL | <https://lists.debian.org/debian-user/> |
| List-Archive | https://lists.debian.org/msgid-search/dfec39b0-aab1-41de-b72f-33bf54db8516@app.fastmail.com |
| Approved | robomod@news.nic.it |
| Lines | 43 |
| Organization | linux.* mail to news gateway |
| Sender | robomod@news.nic.it |
| X-Original-Date | Mon, 11 Dec 2023 17:49:55 +0000 |
| X-Original-Message-ID | <dfec39b0-aab1-41de-b72f-33bf54db8516@app.fastmail.com> |
| X-Original-References | <ZXYZ/t/Um5fIdsBj@axis.corp> <8FF729C3-4B61-42DC-B9B9-866BB5FBBE45@columbus.rr.com> <20231211121229.GB966562@zira.vinc17.org> <67a701d5-93ec-4897-9c4b-77a6021bc59e@columbus.rr.com> <95ff6843-42f5-43de-9be1-7a5527f829c3@its-lehmann.de> <ZXcLrtJvd6hbx7PD@wooledge.org> |
| Xref | csiph.com linux.debian.user:264649 |
Show key headers only | View raw
On Mon, 11 Dec 2023, at 13:16, Greg Wooledge wrote:
> 4) File extensions are used by programs on every operating system.
Certainly on many OSes, but not all.
They're not present on native RISC OS systems (as in ex-Acorn micros).
Filetype data IS stored, but it is in files' metadata.
There's no concept of filetype in file systems used for the MVS side
of z/OS systems. (These days there's also Unix/Linux environments
& of course they do have more familiar file naming structures.)
By convention collections of separate files might all be kept in a set
very vaguely analagous to a directory - though with no parent
directory nor child sub-directories), known as a "PDS". The name
of a PDS is fairly arbitrary (subject to installation conventions &
security restrictions) & the names of files within ("members") also
have no real meaning unless an application chooses to interpret
their names in some special way.
One refers to a PDS as a whole by its name, eg "MY.SAMPLE.PDS"
& to a member within it, eg the file named "FRED", as
"MY.SAMPLE.PDS(FRED)".
While there are conventions for names of these PDSes, there's no
requirement that every file within, say "MY.SAMPLE.ASM" would
contain assembler source. Often only some of the files would do
with others containing notes etc.
If a PDS's name looks like it might contain binary executables AND
it is actually used in a place where that would be expected, then you
can infer that it does do; you wouldn't find plain text notes, sample
data etc alongside the executables (because other characteristics
of those file sets allow them only to hold executables).
You cannot tell from a file's name whether it's held on disk or
(virtual) tape or real tape, nor which device it's currently on.
--
Jeremy Nicoll - my opinions are my own.
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