On 2/17/25 9:58 AM, Greg Wooledge wrote:
On Mon, Feb 17, 2025 at 09:40:31 -0600, David Wright wrote:
I do that with lynx -localhost. One consequence is regular
communications (sometimes by email!) from some banks etc,
complaining that you don't open their emails. Some are so
stupid as to offer
On Mon, Feb 17, 2025 at 09:40:31 -0600, David Wright wrote:
> I do that with lynx -localhost. One consequence is regular
> communications (sometimes by email!) from some banks etc,
> complaining that you don't open their emails. Some are so
> stupid as to offer no way of denying that fact electro
On Mon 17 Feb 2025 at 09:02:11 (+), Jonathan Dowland wrote:
> On Sat Dec 28, 2024 at 4:41 AM GMT, hobie of RMN wrote:
> > What's the best way to handle this? Switch to Thunderbird or
> > claws-mail?
>
> I switched away from (neo)mutt as my primary mailer a little
On 2025-02-17, wrote:
>
> On Sun, Feb 16, 2025 at 01:07:47PM -0500, Greg Wooledge wrote:
>
> [...]
>
>> But this is really all just noise. Use whatever MUA you like.
>
> That's my take, too.
My take is this is a recurrent question concerning Mutt.
On Sat Dec 28, 2024 at 4:41 AM GMT, hobie of RMN wrote:
What's the best way to handle this? Switch to Thunderbird or
claws-mail?
I switched away from (neo)mutt as my primary mailer a little while ago,
but before I did, I was using netsurf-gtk as a viewer for HTML mails in
mutt. It wa
On Sun, Feb 16, 2025 at 01:07:47PM -0500, Greg Wooledge wrote:
[...]
> But this is really all just noise. Use whatever MUA you like.
That's my take, too.
Cheers
--
t
signature.asc
Description: PGP signature
On 2025-02-16, Greg Wooledge wrote:
> On Sun, Feb 16, 2025 at 17:46:18 -, Greg wrote:
>> On 2025-02-16, wrote:
>> >
>> > I don't quite know what you mean by "modern".
>>
>> Mutt was written in 1995. Alpine was publicly released twent
On Sun, Feb 16, 2025 at 17:46:18 -, Greg wrote:
> On 2025-02-16, wrote:
> >
> > I don't quite know what you mean by "modern".
>
> Mutt was written in 1995. Alpine was publicly released twenty years later, in
> 2007.
Mutt is the successor to elm.
On 2025-02-16, wrote:
>
> I don't quite know what you mean by "modern".
Mutt was written in 1995. Alpine was publicly released twenty years later, in
2007.
ient like alpine.
Hm. Last Alpine release is 2.26 [1], from 2022 (basically the one distributed
with Debian), latest Mutt is 2.2.13 (Debian stable has 2.2.12) from 2024. So
I don't quite know what you mean by "modern".
Cheers
[1] https://alpineapp.email/
[2] http://www.mutt.org/
--
t
signature.asc
Description: PGP signature
On 2024-12-28, Olafur Jens Sigurdsson wrote:
>> >
>> > What's the best way to handle this? Switch to Thunderbird or claws-mail?
>> >
>> I simply use lynx to view 99% of HTML E-Mail and the odd one that
>> doesn't view well by that means I feed into my web browser. All on
>> the same machine.
>
On Fri, Dec 27, 2024 at 23:41:39 -0500, hobie of RMN wrote:
> For 20 years I've enjoyed Mutt as my primary mail reader. I used its
> 'bounce' feature to deal with HTML mails, sending them to a webmail
> program on a different server. But now the jellyfish anti-spam daemo
Just a few additional bits added
On Sat, Dec 28, 2024 at 10:23:09AM +, Chris Green wrote:
> hobie of RMN wrote:
> > For 20 years I've enjoyed Mutt as my primary mail reader. I used its
> > 'bounce' feature to deal with HTML mails, sending them to a webm
On Sat, Dec 28, 2024 at 10:23:09AM +, Chris Green wrote:
> hobie of RMN wrote:
> > For 20 years I've enjoyed Mutt as my primary mail reader. I used its
> > 'bounce' feature to deal with HTML mails, sending them to a webmail
> > program on a different serv
hobie of RMN wrote:
> For 20 years I've enjoyed Mutt as my primary mail reader. I used its
> 'bounce' feature to deal with HTML mails, sending them to a webmail
> program on a different server. But now the jellyfish anti-spam daemon
> won't allow me to do th
Hi,
On Fri, Dec 27, 2024 at 11:41:39PM -0500, hobie of RMN wrote:
> For 20 years I've enjoyed Mutt as my primary mail reader. I used its
> 'bounce' feature to deal with HTML mails, sending them to a webmail
> program on a different server.
I also use Mutt. I have Mutt&#
Am Fri, Dec 27, 2024 at 11:41:39PM -0500 schrieb hobie of RMN:
> For 20 years I've enjoyed Mutt as my primary mail reader. I used its
> 'bounce' feature to deal with HTML mails, sending them to a webmail
> program on a different server. But now the jellyfish anti-spam da
On Sat, Dec 28, 2024 at 05:01:15AM +, ghe2001 wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
>
>
>
>
>
>
> On Friday, December 27th, 2024 at 9:41 PM, hobie of RMN
> wrote:
>
> > For 20 years I've enjoyed Mutt as my primary
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Friday, December 27th, 2024 at 9:41 PM, hobie of RMN
wrote:
> For 20 years I've enjoyed Mutt as my primary mail reader. I used its
> 'bounce' feature to deal with HTML mails, sending them to a webmail
> program on
For 20 years I've enjoyed Mutt as my primary mail reader. I used its
'bounce' feature to deal with HTML mails, sending them to a webmail
program on a different server. But now the jellyfish anti-spam daemon
won't allow me to do that; it rejects my bounced emails because &q
On 04/06/2024 07:29, Vincent Lefevre wrote:
On 2024-05-31 19:05:45 +0700, Max Nikulin wrote:
Do you see an attempt to send SIGTERM to mutt before timeout and SIGKILL?
Unfortunately, there was no information from systemd. Some daemons
log a received SIGTERM, but mutt isn't a daemon.
On 2024-05-31 19:05:45 +0700, Max Nikulin wrote:
> Do you see an attempt to send SIGTERM to mutt before timeout and SIGKILL?
Unfortunately, there was no information from systemd. Some daemons
log a received SIGTERM, but mutt isn't a daemon.
> What other processes survived first step
On 31/05/2024 15:10, Vincent Lefevre wrote:
https://github.com/flatpak/xdg-desktop-portal/issues/999
I'm wondering whether there could be a same cause.
I can imagine that mutt may start a GUI handler for some attachment and
that application uses XDG desktop portal. However I would e
On 2024-05-31 10:10:32 +0200, Vincent Lefevre wrote:
> On 2024-05-31 10:02:57 +0700, Max Nikulin wrote:
> > Do you mean that mutt properly exits unless it receives SIGTERM in the
> > course of shutdown process?
>
> I think that this was not the first time I did a shutdown w
On 2024-05-31 10:02:57 +0700, Max Nikulin wrote:
> Do you mean that mutt properly exits unless it receives SIGTERM in the
> course of shutdown process?
I think that this was not the first time I did a shutdown while Mutt
was still running. But this was the first time it did not exit.
>
On 30/05/2024 23:19, Vincent Lefevre wrote:
Have you tried to send SIGTERM to mutt?
I didn't. AFAIK, systemd sends a SIGTERM to all the processes of the
session: that's the
Yes, SIGTERM is the default that systemd tries first. There are various
kill modes, another signal may be
On 2024-05-30 00:19:30 +0700, Max Nikulin wrote:
> On 29/05/2024 07:44, Vincent Lefevre wrote:
> > But I don't understand why there was a timeout. Does this mean that
> > mutt didn't react to SIGTERM? Any reason?
>
> Have you tried to send SIGTERM to mutt?
I
1]: session-2.scope: Stopping timed out.
> > Killing.
> > May 29 01:55:26 qaa systemd[1]: session-2.scope: Killing process 2990
> > (mutt) with signal SIGKILL.
> > May 29 01:55:26 qaa systemd[1]: session-2.scope: Failed with result
> > 'timeout'.
> > Ma
On 29/05/2024 07:44, Vincent Lefevre wrote:
But I don't understand why there was a timeout. Does this mean that
mutt didn't react to SIGTERM? Any reason?
Have you tried to send SIGTERM to mutt? If it ignores this signal or the
reaction is some prompt then you need to find another w
systemd[1]: session-2.scope: Killing process 2990 (mutt)
> with signal SIGKILL.
> May 29 01:55:26 qaa systemd[1]: session-2.scope: Failed with result 'timeout'.
> May 29 01:55:26 qaa systemd[1]: Stopped session-2.scope - Session 2 of User
> vinc17.
> May 29 01:55:26 qaa
During the latest shutdown:
May 29 01:55:05 qaa systemd[1]: Stopping session-2.scope - Session 2 of User
vinc17...
[...]
May 29 01:55:26 qaa systemd[1]: session-2.scope: Stopping timed out. Killing.
May 29 01:55:26 qaa systemd[1]: session-2.scope: Killing process 2990 (mutt)
with signal SIGKILL
Install urlview
Paul M Foster (12024-01-01):
> Of course, it doesn't fix the retarded way Mutt handles links.
To the better of my knowledge, Mutt does not handle links at all. Please
refrain from calling it retarded.
> For those
> fami
wrapped.
>
> This is "quoted-printable" encoding. You need to use a properly decoded
> version of the file, rather than the raw text.[1]
>
> > As a solution, I took that email from my mutt mail file and stripped out
> > all the headers and non-HTML content. Then I f
On Mon, 1 Jan 2024, Nicolas George wrote:
> This was not a reply to the original mail. You might consider using a
> MUA with proper threading to better understand what is going on.
from the negative nature of your communications
every one understands what's going on
fxkl4...@protonmail.com (12024-01-01):
> actually the question was
> " what is wrapping the lines on my incoming emails, and how do I fix it "
> please try to keep up
This was not a reply to the original mail. You might consider using a
MUA with proper threading to better understand what is going
On Mon, 1 Jan 2024, Nicolas George wrote:
> gene heskett (12024-01-01):
>> Most browsers to well with such as long as the link is surrounded by
>> the left-right arrows delineate the links contents even if it is wrapped to
>> several lines on your screen.
>
> Please try to keep up with the contex
gene heskett (12024-01-01):
> Most browsers to well with such as long as the link is surrounded by
> the left-right arrows delineate the links contents even if it is wrapped to
> several lines on your screen.
Please try to keep up with the context of the discussion, we were
talking about links di
On 1/1/24 11:52, Nicolas George wrote:
Greg Wooledge (12024-01-01):
It's been my experience that the hyperlinks I'm meant to click are so
long that they wrap around the terminal width multiple times. This
makes copy/pasting them tedious at best, and even then it still
sometimes fails for me.
Greg Wooledge:
> It's been my experience that the hyperlinks I'm meant to click are so
> long that they wrap around the terminal width multiple times. This
> makes copy/pasting them tedious at best, and even then it still
> sometimes fails for me.
My wife has the same problem.
--
John Hasler
j.
Greg Wooledge (12024-01-01):
> It's been my experience that the hyperlinks I'm meant to click are so
> long that they wrap around the terminal width multiple times. This
> makes copy/pasting them tedious at best, and even then it still
> sometimes fails for me.
Surprising. The graphical web brows
Hello,
On Mon, Jan 01, 2024 at 09:23:03AM -0500, Greg Wooledge wrote:
> Passing the entire text/html part to an actual web browser has been
> what works best for me.
Me too. I'll do the mailcap thing to visually skim the text/html
part with w3m, but there are so many broken HTML messes that I'm
o
On Mon, Jan 01, 2024 at 11:42:59AM +0100, Nicolas George wrote:
> Greg Wooledge (12023-12-31):
> > Have your browser load THAT file.
>
> Or just have this:
>
> text/html; lynx -force_html -dump %s; copiousoutput
>
> in your .mailcap file. Possibly along with:
>
> auto_view text/html
>
> in the
Greg Wooledge (12023-12-31):
> Have your browser load THAT file.
Or just have this:
text/html; lynx -force_html -dump %s; copiousoutput
in your .mailcap file. Possibly along with:
auto_view text/html
in the .muttrc.
Regards,
--
Nicolas George
On 31 Dec 2023 22:51 -0500, from pa...@quillandmouse.com (Paul M Foster):
> As a solution, I took that email from my mutt mail file and stripped out
> all the headers and non-HTML content. Then I fed that to my browser. Sorta
> worked. However, the button I was supposed to click di
> Like everyone else, I get emails with links in them which need to be
> clicked to change passwords, verify identity and such. I was a loyal mutt
> user for years, but problems with URLs caused me to eventually change to
> claws-mail. Recently, I tweaked my mutt config, and URLs se
oded
version of the file, rather than the raw text.[1]
> As a solution, I took that email from my mutt mail file and stripped out
> all the headers and non-HTML content. Then I fed that to my browser.
If you received a correctly formatted email, it should contain one or more
parts, each of
Folks:
Like everyone else, I get emails with links in them which need to be
clicked to change passwords, verify identity and such. I was a loyal mutt
user for years, but problems with URLs caused me to eventually change to
claws-mail. Recently, I tweaked my mutt config, and URLs seemed to work
On Tue, Dec 12, 2023 at 06:04:04AM +0800, jeremy ardley wrote:
[...]
> If you look at the NTFS file system [...]
> Underneath the hood of a NTFS file is alternate data streams (ADS). That is
> a single file can contain main different 'sub files' of completely different
> content type. Each ADS h
On 12/12/23 01:49, Jeremy Nicoll wrote:
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.)
If you look at the NTFS file system - supported by m
debian-u...@howorth.org.uk wrote:
> songbird wrote:
>> wrote:
>> > On Sun, Dec 10, 2023 at 01:28:20PM -0500, songbird wrote:
>> >> wrote:
>>
>> there is rarely a need to e-mail me directly.
>>
>> >> ...
>> >> > That's why I cringe when people name executables "foo.sh". What
>> >> > do
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 n
ere is
> > > > > > > an image to
> > > > > > > view, viewing it in neomutt calls up one of the ImageMagick
> > > > > > > programs. I've set
> > > > > > > the mailcap_path variable in my neomutt config to point to
On Mon, Dec 11, 2023 at 10:10:31AM -0500, Stefan Monnier wrote:
[...]
> I think what you're saying is that it would make sense to use
> a dedicated extension for executables, like, say, `.exe`,
> since "all users rely on it being" executable.
I'd prefer ".com", but hey ;-)
> FWIW, I agree, but
On Mon 11 Dec 2023 at 10:07:28 (+1100), Zenaan Harkness wrote:
> > Second, how do I fix this so that mutt uses feh to display images?
>
> Here is my mailcap entry, which works for me - had to deal with
> annoying filename munging by mutt, and getting the "close the viewer"
songbird wrote:
> wrote:
> > On Sun, Dec 10, 2023 at 01:28:20PM -0500, songbird wrote:
> >> 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 i
On 2023-12-11 09:34:09 -0500, Pocket wrote:
> On 12/11/23 09:04, Vincent Lefevre wrote:
> > On 2023-12-11 08:16:30 -0500, Greg Wooledge wrote:
> > > 2) When *receiving* email, mutt will use the sender's MIME type label
> > > to decide how to deal with the a
> (Note that I'd even make a difference: where the implementation matters,
> e.g. some shell code to be sourced in, I'd be more lenient in calling
> the thing ".sh": after all, its users rely on it being shell code. When
> you can change the implementation without changing the function, e.g.
> a sh
~/.config/mutt/mailcap-mutt, which is
a specially crafted subset of /etc/mailcap with a few additions
(like converting webp to a jpeg rather than opening in gimp,
and playing midi files the way I want).
and
set an entry in there for image/jpg to point to /usr/bin/feh. I&#
On Mon, Dec 11, 2023 at 08:52:37AM -0600, David Wright wrote:
> On Sun 10 Dec 2023 at 15:51:02 (-0500), Pocket wrote:
[...]
> > File names in Linux are a character string of 255 chars. Again there are
> > not file extensions in a Linux file name.
> >
> > People are conflating the issue.
> >
>
t;>> I've set
> >>>> the mailcap_path variable in my neomutt config to point to ~/.mailcap,
> >
> > Similarly, I point it to ~/.config/mutt/mailcap-mutt, which is
> > a specially crafted subset of /etc/mailcap with a few additions
> > (like convertin
On 12/11/23 09:34, Vincent Lefevre wrote:
On 2023-12-11 15:16:57 +0100, to...@tuxteam.de wrote:
On Mon, Dec 11, 2023 at 02:58:01PM +0100, Vincent Lefevre wrote:
I do not care about the "microsoft world", and I doubt that this is
required there at the low level (what would be the equivalent of
On Mon, Dec 11, 2023 at 03:34:28PM +0100, Vincent Lefevre wrote:
> On 2023-12-11 15:16:57 +0100, to...@tuxteam.de wrote:
> > On Mon, Dec 11, 2023 at 02:58:01PM +0100, Vincent Lefevre wrote:
> > > I do not care about the "microsoft world", and I doubt that this is
> > > required there at the low lev
On 2023-12-11 15:16:57 +0100, to...@tuxteam.de wrote:
> On Mon, Dec 11, 2023 at 02:58:01PM +0100, Vincent Lefevre wrote:
> > I do not care about the "microsoft world", and I doubt that this is
> > required there at the low level (what would be the equivalent of the
> > Linux kernel) [...]
>
> This
On 12/11/23 09:04, Vincent Lefevre wrote:
On 2023-12-11 08:16:30 -0500, Greg Wooledge wrote:
2) When *receiving* email, mutt will use the sender's MIME type label
to decide how to deal with the attachment.
But the notion of filename extension is even used in this context too.
Quotin
On Mon, Dec 11, 2023 at 02:58:01PM +0100, Vincent Lefevre wrote:
[...]
> I do not care about the "microsoft world", and I doubt that this is
> required there at the low level (what would be the equivalent of the
> Linux kernel) [...]
This depends: the FAT file system (which still is the lowest c
On 2023-12-11 08:16:30 -0500, Greg Wooledge wrote:
> 2) When *receiving* email, mutt will use the sender's MIME type label
>to decide how to deal with the attachment.
But the notion of filename extension is even used in this context too.
Quoting the
On 2023-12-11 07:32:30 -0500, Pocket wrote:
>
> On 12/11/23 07:12, Vincent Lefevre wrote:
> > On 2023-12-10 15:51:02 -0500, Pocket wrote:
> > > On Dec 10, 2023, at 3:05 PM, David Wright
> > > wrote:
> > > > ¹ Re the argument raging in this thread about "extension", the
> > > > term is clearly
> no goal with this thread.
>
>
> I would ask you to continue this discussion elsewhere.
It's on topic, so there's no call to ask for the discussion to be
discontinued here.
The facts are pretty simple:
1) When *sending* email, mutt uses the file's extension to decide
David writes:
> Hi, the filename extension is usually irrelevant on Linux, because
> Linux tools typically
> use the standard 'file' command to inspect the content of the
> fileinstead of relying on
> the filename to indicate content.
It is very often not irrelevant for files that you might want
On Monday, 11 Dec 2023 at 07:32, Pocket wrote:
> No it is microsoft non sense
I'm not an MS fanboi but please stop blaming MS for something they did
not invent!
--
Eric S Fraga via gnus (Emacs 30.0.50 2023-09-14) on Debian 12.2
All,
I do not see the relevance of the discussion about file name extensions,
types, suffixes for Debian. Even more so as you are at the stage of
repeating statements without bringing new value. In fact, there seems to
be no goal with this thread.
I would ask you to continue this discussion
On 12/11/23 07:12, Vincent Lefevre wrote:
On 2023-12-10 15:51:02 -0500, Pocket wrote:
On Dec 10, 2023, at 3:05 PM, David Wright wrote:
¹ Re the argument raging in this thread about "extension", the
term is clearly appropriate, as a glance at /etc/mime.types
demonstrates. The literature is
On 12/11/23 06:39, Vincent Lefevre wrote:
On 2023-12-08 17:06:15 -0500, Pocket wrote:
On 12/8/23 16:53, David wrote:
Hi, the filename extension is usually irrelevant on Linux, because
Linux tools typically
use the standard 'file' command to inspect the content of the
fileinstead of relying on
On 2023-12-10 15:51:02 -0500, Pocket wrote:
> On Dec 10, 2023, at 3:05 PM, David Wright wrote:
> > ¹ Re the argument raging in this thread about "extension", the
> > term is clearly appropriate, as a glance at /etc/mime.types
> > demonstrates. The literature is full of the term.
> >
> > I woul
On 2023-12-08 17:06:15 -0500, Pocket wrote:
> On 12/8/23 16:53, David wrote:
> > Hi, the filename extension is usually irrelevant on Linux, because
> > Linux tools typically
> > use the standard 'file' command to inspect the content of the
> > fileinstead of relying on
> > the filename to indicate
wrote:
> On Sun, Dec 10, 2023 at 01:28:20PM -0500, songbird wrote:
>> 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
> Finally, occasionally I need to cleanly dump html, this one seems a bit
> simpler:
>
> text/html; lynx -stdin -dump -width=$COLS; copiousoutput; compose=vim %s
I meant "cleanly _view_ html ..."
> Second, how do I fix this so that mutt uses feh to display images?
Here is my mailcap entry, which works for me - had to deal with
annoying filename munging by mutt, and getting the "close the viewer"
bit working - this is quite a few years ago and now I can't even
remember w
e:
>>>>
>>>> I'm on Debian bookworm, using neomutt for email. Where there is an image to
>>>> view, viewing it in neomutt calls up one of the ImageMagick programs. I've
>>>> set
>>>> the mailcap_path variable in my neomutt confi
On Sun 10 Dec 2023 at 19:48:29 (+0100), to...@tuxteam.de wrote:
> On Sun, Dec 10, 2023 at 01:28:20PM -0500, songbird wrote:
> > wrote:
> > ...
> > > 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)?
> >
is an image
> > > to
> > > view, viewing it in neomutt calls up one of the ImageMagick programs.
> > > I've set
> > > the mailcap_path variable in my neomutt config to point to ~/.mailcap,
Similarly, I point it to ~/.config/mutt/mailcap-mutt, which
On Sun, Dec 10, 2023 at 01:28:20PM -0500, songbird wrote:
> wrote:
> ...
> > 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?
>
>
wrote:
...
> 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. :)
On Sun, Dec 10, 2023 at 04:15:22PM -, Curt wrote:
> On 2023-12-09, Eric S Fraga wrote:
> > On Friday, 8 Dec 2023 at 17:06, Pocket wrote:
> >> In Unix and Linux there isn't a file extension, that is a microsoft
> >> invention.
> >
> > Predates MS by years. Systems like RSTS/E on PDP-11s, just
On 2023-12-09, Eric S Fraga wrote:
> On Friday, 8 Dec 2023 at 17:06, Pocket wrote:
>> In Unix and Linux there isn't a file extension, that is a microsoft
>> invention.
>
> Predates MS by years. Systems like RSTS/E on PDP-11s, just to name one.
They certainly are convenient.
I must be stupid o
On Friday, 8 Dec 2023 at 17:06, Pocket wrote:
> In Unix and Linux there isn't a file extension, that is a microsoft
> invention.
Predates MS by years. Systems like RSTS/E on PDP-11s, just to name one.
--
Eric S Fraga via gnus (Emacs 30.0.50 2023-09-14) on Debian 12.2
On 12/8/23 17:55, Greg Wooledge wrote:
On Fri, Dec 08, 2023 at 04:50:04PM -0600, John Hasler wrote:
Greg writes:
cc(1) and make(1) would like to have a talk with you.
Those are applications and can do whatever they want. The OS does not
care about extensions.
What do you consider "the OS"
On 12/8/23 18:17, Greg Wooledge wrote:
On Fri, Dec 08, 2023 at 05:59:58PM -0500, Pocket wrote:
On 12/8/23 17:54, Greg Wooledge wrote:
cc(1) looks at the file extension to decide what kind of content each
named argument file is expected to contain.
No it looks for a suffix
So Debian files ha
On Fri, Dec 08, 2023 at 05:59:58PM -0500, Pocket wrote:
> On 12/8/23 17:54, Greg Wooledge wrote:
> > cc(1) looks at the file extension to decide what kind of content each
> > named argument file is expected to contain.
> No it looks for a suffix
So Debian files have "suffixes" and Windows files h
On 2023-12-08 22:55, Greg Wooledge wrote:
On Fri, Dec 08, 2023 at 04:50:04PM -0600, John Hasler wrote:
Greg writes:
> cc(1) and make(1) would like to have a talk with you.
Those are applications and can do whatever they want. The OS does not
care about extensions.
What do you consider "the O
hich decides what
Content-type header to generate for a given static file based on its
extension. I would imagine other web servers do the same thing.
Apache is an application that looks for a file suffix
And hey, I'm using mutt to compose and send this email. If I were to
attach a
On Fri, Dec 08, 2023 at 04:50:04PM -0600, John Hasler wrote:
> Greg writes:
> > cc(1) and make(1) would like to have a talk with you.
>
> Those are applications and can do whatever they want. The OS does not
> care about extensions.
What do you consider "the OS" to be, then?
7;s also Apache, which decides what
Content-type header to generate for a given static file based on its
extension. I would imagine other web servers do the same thing.
And hey, I'm using mutt to compose and send this email. If I were to
attach a file to this message, mutt would look at its e
On 12/8/23 17:41, Pocket wrote:
On 12/8/23 17:31, Greg Wooledge wrote:
On Fri, Dec 08, 2023 at 05:06:15PM -0500, Pocket wrote:
In Unix and Linux there isn't a file extension, that is a microsoft
invention.
cc(1) and make(1) would like to have a talk with you.
Linux/Unix filenaming specs w
Greg writes:
> cc(1) and make(1) would like to have a talk with you.
Those are applications and can do whatever they want. The OS does not
care about extensions.
--
John Hasler
j...@sugarbit.com
Elmwood, WI USA
On 12/8/23 17:31, Greg Wooledge wrote:
On Fri, Dec 08, 2023 at 05:06:15PM -0500, Pocket wrote:
In Unix and Linux there isn't a file extension, that is a microsoft
invention.
cc(1) and make(1) would like to have a talk with you.
Linux/Unix filenaming specs would like to inform you.
file spe
On Fri, Dec 08, 2023 at 05:06:15PM -0500, Pocket wrote:
> In Unix and Linux there isn't a file extension, that is a microsoft
> invention.
cc(1) and make(1) would like to have a talk with you.
play" alternative to feh with update-alternatives. Still, mutt is
calling an imagemagick program to display jpgs.
First, if alternatives doesn't point to the imagemagick program, and the
mailcap file doesn't point to it, and there's nothing in the neomutt config
pointing to the
en
> > > set
> > ↑↑↑ try jpeg
> >
> > > the "display" alternative to feh with update-alternatives. Still, mutt is
> > > calling an imagemagick program to display jpgs.
> > >
> > > First, if altern
1 - 100 of 4843 matches
Mail list logo
