;> I believed there are at least 4 ways (besides settings specific to
> >> particular applications)
> >> - *browser alternatives
> >> - BROWSER environment
> >> - mailcap for text/html
> >> - XDG configuration
> >>
> >> sensible-browser,
des settings specific to
>> particular applications)
>> - *browser alternatives
>> - BROWSER environment
>> - mailcap for text/html
>> - XDG configuration
>>
>> sensible-browser, "open", and xdg-open just use some of these options.
>
> There
On 13/02/2025 09:19, Greg Wooledge wrote:
On Thu, Feb 13, 2025 at 08:56:47 +0700, Max Nikulin wrote:
- *browser alternatives
- BROWSER environment
- mailcap for text/html
I have realized that I do not have an example of an application that
determines https: scheme handler from mailcap (it is
gt; - *browser alternatives
> - BROWSER environment
> - mailcap for text/html
> - XDG configuration
>
> sensible-browser, "open", and xdg-open just use some of these options.
There's also all the MIME confguration.
--
Chris Green
·
particular applications)
> - *browser alternatives
> - BROWSER environment
> - mailcap for text/html
> - XDG configuration
Yes, but mailcap and XDG aren't Debian specific. Alternatives and
the $BROWSER variable (which is what the sensible-browser shell script
uses) are Debia
On 13/02/2025 01:26, Greg Wooledge wrote:
Now Debian has*two* completely separate
ways to specify a default application for a role.
I believed there are at least 4 ways (besides settings specific to
particular applications)
- *browser alternatives
- BROWSER environment
- mailcap for text
On Wed, Feb 12, 2025 at 10:34:32 -0600, David Wright wrote:
> urlCommand "sensible-browser '%s'"
hobbit:~$ type -a sensible-browser
sensible-browser is /usr/bin/sensible-browser
sensible-browser is /bin/sensible-browser
hobbit:~$ ls -l /usr/bin/sensible-browser
-rwxr-xr-x 1 root root 1290
On 2025-02-12, Nicolas George wrote:
> Greg (HE12025-02-12):
>> What is going on? You suggested examining the source code.
>
> No, I suggested reading the documentation. Others have suggested other
> avenues that lead to understanding. These are good answers. The
> suggestions to uninstall and ran
Greg (HE12025-02-12):
> What is going on? You suggested examining the source code.
No, I suggested reading the documentation. Others have suggested other
avenues that lead to understanding. These are good answers. The
suggestions to uninstall and randomly fiddle with the order are
polluting the go
On 2025-02-12, Nicolas George wrote:
>
> The only way to achieve a reliable result is to understand what is going
> on. I am flabbergasted that so many people on this list do not start
What is going on? You suggested examining the source code. For the end
user, this might be arduous task at best.
fixated on order of
> installation, and that might be a fix for /etc/alternatives, and
> with luck perhaps even /etc/{mailcap,mime.types}, but is unlikely
> to affect configuration files in /home, environmental variables,
> and whatever is hardwired in programs themselves.
It's
Greg (HE12025-02-12):
> Simply reversing the installation order of the two browsers seems the
> most direct and easiest solution.
It might achieve the result. A solution…
What will the OP do if they install another browser to try something and
it becomes the default one? Uninstall them all and r
whether xfce-terminal respects /etc/xdg/mimeapps.list or
> ~/.config/mimeapps.list. My expectation it should.
The OP needs to delve into what's calling up the browser in each and
every case, unfortunately. Some here have fixated on order of
installation, and that might be a fix for /et
On 2025-02-12, Brad Rogers wrote:
>
> On Wed, 12 Feb 2025 15:36:46 - (UTC)
> Greg wrote:
>
> Hello Greg,
>
>>What exactly is he after? I was under the impression it was setting the
>>default browser to Vivaldi.
>
> Yes, but as has been explained, there are multiple ways in which a
> browser c
Chris Green wrote:
> Anssi Saari wrote:
> > Chris Green writes:
> >
> > > Installing epiphany just added it as a choice but left vivaldi as the
> > > configured browser, but still epiphany grabbed everything.
> >
> > Have you considered you may get better information if you actually
> > define
On Wed, 12 Feb 2025 15:36:46 - (UTC)
Greg wrote:
Hello Greg,
>What exactly is he after? I was under the impression it was setting the
>default browser to Vivaldi.
Yes, but as has been explained, there are multiple ways in which a
browser can be chosen. Some, most notably, circumventing sys
On 12/02/2025 22:09, Greg wrote:
On 2025-02-12, Max Nikulin wrote:
Certainly, but before delving into source code I would try the standard
(XDG) way to configure media types and applications associations.
Unfortunately, as Greg Wooledge has already pointed out, there is no
universal standard.
Greg wrote:
> On 2025-02-12, Nicolas George wrote:
> > Max Nikulin (HE12025-02-12):
> >> I would not be surprised if it is not explicitly documented.
> >
> > At worst, the source code is the documentation.
>
> I think Chris had the right idea. Install Epiphany first, and then
> Vivaldi, instead
On 2025-02-12, Brad Rogers wrote:
>
> On Wed, 12 Feb 2025 15:09:38 - (UTC)
> Greg wrote:
>
> Hello Greg,
>
>>Simply reversing the installation order of the two browsers seems the
>>most direct and easiest solution.=20
>
> Still with, of course, no guarantee of successfully achieving exactly
>
On Wed, 12 Feb 2025 15:09:38 - (UTC)
Greg wrote:
Hello Greg,
>Simply reversing the installation order of the two browsers seems the
>most direct and easiest solution.
Still with, of course, no guarantee of successfully achieving exactly
what Chris is after.
--
Regards _ "Valid si
On 2025-02-12, Max Nikulin wrote:
> On 12/02/2025 20:55, Nicolas George wrote:
>> Max Nikulin (HE12025-02-12):
>>> I would not be surprised if it is not explicitly documented.
>>
>> At worst, the source code is the documentation.
>
> Certainly, but before delving into source code I would try the
On 12/02/2025 20:55, Nicolas George wrote:
Max Nikulin (HE12025-02-12):
I would not be surprised if it is not explicitly documented.
At worst, the source code is the documentation.
Certainly, but before delving into source code I would try the standard
(XDG) way to configure media types and
On 2025-02-12, Nicolas George wrote:
> Max Nikulin (HE12025-02-12):
>> I would not be surprised if it is not explicitly documented.
>
> At worst, the source code is the documentation.
I think Chris had the right idea. Install Epiphany first, and then
Vivaldi, instead of the other way around.
Pro
On 2025-02-12, Chris Green wrote:
>>
>> If you want a Linux way to solve the issue: first, read the
>> documentation of xfce-terminal to see how it decides which web browser
>> to run; then read the documentation of that mechanism to see how to
>> configure it.
>>
> I have looked in the xfce4-te
Max Nikulin (HE12025-02-12):
> I would not be surprised if it is not explicitly documented.
At worst, the source code is the documentation.
Regards,
--
Nicolas George
Nicolas George wrote:
> Chris Green (12025-02-12):
> > I'm just wondering if a way round the issue may be to unistall
> > vivaldi, then install epiphany, then re-install vivaldi. It might be
> > that just doing 'apt reinstall vivaldi' will get me back to where I
> > want to be.
>
> That might be
Greg Wooledge wrote:
> On Wed, Feb 12, 2025 at 10:02:13 +, Chris Green wrote:
> > debian-u...@howorth.org.uk wrote:
> > > The other user does NOT have the same settings as me. They have
> > > their own set of plugins and settings as Tomas has pointed out. You
> > > very much can install someth
On Wed, Feb 12, 2025 at 07:18:23AM -0500, Greg Wooledge wrote:
> On Wed, Feb 12, 2025 at 10:06:53 +, Chris Green wrote:
> > The specific thing that bit me when I installed epiphany was clicking
> > on a web link in a terminal (xfce4-terminal) window. Instead of
> > opening the link in the alrea
On Wed, Feb 12, 2025 at 10:06:53 +, Chris Green wrote:
> The specific thing that bit me when I installed epiphany was clicking
> on a web link in a terminal (xfce4-terminal) window. Instead of
> opening the link in the already running vivaldi, in another workspace
> (which is the way I like it)
On 12/02/2025 17:23, Nicolas George wrote:
If you want a Linux way to solve the issue: first, read the
documentation of xfce-terminal to see how it decides which web browser
to run;
I would not be surprised if it is not explicitly documented. Perhaps
XFCE has a configuration menu. Most GUI app
On Wed, Feb 12, 2025 at 10:02:13 +, Chris Green wrote:
> debian-u...@howorth.org.uk wrote:
> > The other user does NOT have the same settings as me. They have
> > their own set of plugins and settings as Tomas has pointed out. You
> > very much can install something for one user and not for ano
debian-u...@howorth.org.uk wrote:
> Chris Green wrote:
> > debian-u...@howorth.org.uk wrote:
> > > Chris Green wrote:
> > > > songbird wrote:
> > > > > Chris Green wrote:
> > > > > ...
> > > > > > It would be much easier if I could simply tell epiphany (or
> > > > > > another browser) **
Chris Green (12025-02-12):
> I'm just wondering if a way round the issue may be to unistall
> vivaldi, then install epiphany, then re-install vivaldi. It might be
> that just doing 'apt reinstall vivaldi' will get me back to where I
> want to be.
That might be a way, but it would be less efficien
Anssi Saari wrote:
> Chris Green writes:
>
> > Installing epiphany just added it as a choice but left vivaldi as the
> > configured browser, but still epiphany grabbed everything.
>
> Have you considered you may get better information if you actually
> define this "everything"? For me it's the
Chris Green writes:
> Installing epiphany just added it as a choice but left vivaldi as the
> configured browser, but still epiphany grabbed everything.
Have you considered you may get better information if you actually
define this "everything"? For me it's the small handful of apps I
mentioned
On Wed, Feb 12, 2025 at 07:24:28AM +, Chris Green wrote:
[...]
> Er, but that's the whole problem!!! I installed epiphany (using apt)
> and it **did** force all 'the other users' (including me) to use it.
> You have described the problem in a nutshell! :-)
Then, it seems that it is alternat
Chris Green wrote:
> debian-u...@howorth.org.uk wrote:
> > Chris Green wrote:
> > > songbird wrote:
> > > > Chris Green wrote:
> > > > ...
> > > > > It would be much easier if I could simply tell epiphany (or
> > > > > another browser) **not** to try and become the default for
> > > > >
to...@tuxteam.de wrote:
> [-- text/plain, encoding quoted-printable, charset: utf-8, 39 lines --]
>
> On Tue, Feb 11, 2025 at 08:21:02PM +, Chris Green wrote:
> > debian-u...@howorth.org.uk wrote:
> > > Chris Green wrote:
> > > > songbird wrote:
> > > > > Chris Green wrote:
> > > > > ...
>
On Tue, Feb 11, 2025 at 08:21:02PM +, Chris Green wrote:
> debian-u...@howorth.org.uk wrote:
> > Chris Green wrote:
> > > songbird wrote:
> > > > Chris Green wrote:
> > > > ...
> > > > > It would be much easier if I could simply tell epiphany (or
> > > > > another browser) **not** to try an
debian-u...@howorth.org.uk wrote:
> Chris Green wrote:
> > songbird wrote:
> > > Chris Green wrote:
> > > ...
> > > > It would be much easier if I could simply tell epiphany (or
> > > > another browser) **not** to try and become the default for
> > > > everything, rather than having to try and
Chris Green wrote:
> songbird wrote:
> > Chris Green wrote:
> > ...
> > > It would be much easier if I could simply tell epiphany (or
> > > another browser) **not** to try and become the default for
> > > everything, rather than having to try and unset all the changes
> > > it has made.
> >
Chris Green wrote:
> songbird wrote:
>> Chris Green wrote:
>> ...
>> > It would be much easier if I could simply tell epiphany (or another
>> > browser) **not** to try and become the default for everything, rather
>> > than having to try and unset all the changes it has made.
>>
>> Chris, for s
songbird wrote:
> Chris Green wrote:
> ...
> > It would be much easier if I could simply tell epiphany (or another
> > browser) **not** to try and become the default for everything, rather
> > than having to try and unset all the changes it has made.
>
> Chris, for something like testing i woul
Chris Green wrote:
...
> It would be much easier if I could simply tell epiphany (or another
> browser) **not** to try and become the default for everything, rather
> than having to try and unset all the changes it has made.
Chris, for something like testing i would just set up
another user.
On 10/02/2025 22:25, Chris Green wrote:
It would be much easier if I could simply tell epiphany (or another
browser) **not** to try and become the default for everything, rather
than having to try and unset all the changes it has made.
Installing an application may change order of candidates in
/stackoverflow.com/questions/41172692/xdg-open-does-not-open-the-default-browser#comments-link-41172692>.
>
>
>
> Others may use MIME, in which case you would configure some file
> or other. It used to be ~/.mailcap but apparently XDG is trying to
> move this to ~/.config/m
which is described at
<https://stackoverflow.com/questions/41172692/xdg-open-does-not-open-the-default-browser#comments-link-41172692>.
Others may use MIME, in which case you would configure some file
or other. It used to be ~/.mailcap but apparently XDG is trying to
move this to ~/.config/mimeapps.list (acco
Anssi Saari wrote:
> Chris Green writes:
>
> > However, when I install epiphany it takes over every single thing that
> > web browsers can do which is very frustrating, I only want to run it
> > explicitly for testing. Is there any way to prevent the install
> >
Chris Green writes:
> However, when I install epiphany it takes over every single thing that
> web browsers can do which is very frustrating, I only want to run it
> explicitly for testing. Is there any way to prevent the install
> changing all the mailcap and mime settings etc.
o which is very frustrating, I only want to run it
explicitly for testing. Is there any way to prevent the install
changing all the mailcap and mime settings etc.?
(I've got my vivaldi default settings back by purging epiphany but
that's a bit extreme!)
--
Chris Green
·
nteresting to see another user of debbugs out there Today, besides
Debian!)
> However at least one developer was against wrappers:
…
Thank you for sharing these upstream bugs. They make for fascinating
(if occasionally horrifying) reading.
> Finally, I think that s-nail should ignore malfor
On 2024-05-15 17:51, Max Nikulin wrote:
I have filed
https://bugs.debian.org/1071036
update-mime does not escape semicolon in .desktop Exec entries
Thanks! I should have done that, but I've postponed it because I felt I
didn't know enough about the context. (I just run Emacs on a Debian
ser
o mention \n, \t, \s
https://git.savannah.gnu.org/cgit/emacs.git/tree/lisp/dired-aux.el#n1364
shell-command-guess-xdg function
Finally, I think that s-nail should ignore malformed mailcap entries.
On 16/05/2024 14:48, Jonathan Dowland wrote:
Please do not CC me for listmail.
You still decided
On Wed May 15, 2024 at 4:51 PM BST, Max Nikulin wrote:
> On 07/05/2024 23:24, Max Nikulin wrote:
> >> On 2024-05-06 17:04, Max Nikulin wrote:
> >>> So doubled backslashes (as in .desktop files) are correct.
> >>>
> >>> What is wrong is lack of backslashes added before ";" and it is a bug.
>
> I hav
semicolon in .desktop Exec entries
This particular bug almost certainly may be fixed by adding an extra
line of perl code.
However 2 layer of quoting in .desktop files: special rules for Exec and
general for any strings require more work to get entries properly
escaped for mailcap in general
On 07/05/2024 18:40, Jesper Dybdal wrote:
On 2024-05-06 16:24, Max Nikulin wrote:
2. It does not skip x-scheme-handler/* entries. Are there applications
that may use such entries?
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=291015
mime-support: run‐mailcap to understand URL notation and
On 2024-05-06 16:24, Max Nikulin wrote:
On 06/05/2024 20:27, Greg Wooledge wrote:
On Mon, May 06, 2024 at 02:53:10PM +0200, Jesper Dybdal wrote:
s-nail: $MAILCAPS: /etc/mailcap: text/english: ignored unknown
string/command: then exec emacsclient --alternate-editor =
--display=\\"\\$DI
On 06/05/2024 21:24, Max Nikulin wrote:
It seems there are a couple of bugs in update-mime:
1. It does not perform an unquote pass that should retain only a half of
backslashes from Exec field of .desktop file.
I was wrong here. mailcap(5):
(In fact, the backslash can be used to quote any
On 06/05/2024 21:41, David Wright wrote:
On Mon 06 May 2024 at 14:53:10 (+0200), Jesper Dybdal wrote:
* In Bookworm:
mailcap/stable,now 3.70+nmu1 all [installed,automatic]
j-nail/stable,now 14.9.24-2 amd64 [installed]
↑
Has anyone else seen this?
Do you have emacs installed
On Mon 06 May 2024 at 14:53:10 (+0200), Jesper Dybdal wrote:
> The package versions involved are:
> * in Bullseye:
> mailcap/oldstable,now 3.69 all [installed,automatic]
> s-nail/oldstable,now 14.9.22-1 amd64 [installed]
> * In Bookworm:
> mailcap/stable,now 3.70+n
On 06/05/2024 20:27, Greg Wooledge wrote:
On Mon, May 06, 2024 at 02:53:10PM +0200, Jesper Dybdal wrote:
s-nail: $MAILCAPS: /etc/mailcap: text/english: ignored unknown
string/command: then exec emacsclient --alternate-editor =
--display=\\"\\$DISPLAY\\" \\"\\$@\\"
The
connection with viewing messages. Here is a sample:
s-nail: $MAILCAPS: /etc/mailcap: x-scheme-handler/mailto: ignored
unknown string/command: u = \\${u//\\"/\\"}
s-nail: $MAILCAPS: /etc/mailcap: text/english: ignored unknown
string/command: then exec emacsclient --alternat
wing messages. Here is a sample:
> > s-nail: $MAILCAPS: /etc/mailcap: x-scheme-handler/mailto: ignored
> > unknown string/command: u = \\${u//\\"/\\\\\\"}
> > s-nail: $MAILCAPS: /etc/mailcap: text/english: ignored unknown
> > string/command: then exec e
I use s-nail as my mailx command (selected using the Debian
"alternatives" mechanism).
Since I upgraded from Bullseye to Bookworm, s-nail now shows a bunch of
error messages in connection with viewing messages. Here is a sample:
s-nail: $MAILCAPS: /etc/mailcap: x-scheme-hand
hing like this once about every several
> years and it's all new again. Sigh...
Yes, same here, which is partly why I tried tracking it through.
I actually have a ~/.mutt/mailcap-mutt defined that matches only
a very select set of file types.
Cheers,
David.
On Thu, Sep 16, 2021 at 07:43:25AM -0400, Greg Wooledge wrote:
Unfortunately, it breaks in Bourne-family shells.
snip
In Bourne/POSIX/bash, semicolon is a command terminator or separator,
and may not appear by itself, or at the start of a command. It may
appear at the end.
Good catch! I neve
On Thu, Sep 16, 2021 at 08:47:32AM +0100, Jonathan Dowland wrote:
> On Wed, Sep 15, 2021 at 02:01:23PM -0400, Greg Wooledge wrote:
> > I don't know why there's a ";" in front of it.
>
> That's (part of) my shell prompt. It's a convention originating in the
> rc shell (although I learned of it from
the line:
>
> text/x-diff diff patch
> Your attachment had the extension ".patch", so it searches your
> and the system's mailcap files for "text/x-diff", fails to find it,
> and eventually hits the default entry:
>
>
* On 2021 16 Sep 02:35 -0500, Andrei POPESCU wrote:
> For neomutt in buster I have this in .neomuttrc:
>
> # neomutt disabled viewing text/* as text (except text/plain)
> # re-enable common file types received (requires corresponding .mailcap entry)
> auto_view text/x-diff
>
On Thu, Sep 16, 2021 at 08:47:32AM +0100, Jonathan Dowland wrote:
> On Wed, Sep 15, 2021 at 02:01:23PM -0400, Greg Wooledge wrote:
[...]
> >I don't know why there's a ";" in front of it.
>
> That's (part of) my shell prompt [...]
aaah :-)
Thanks for clearing that up. My hunch was at least
problem down to either mailcap or
neomutt. It seems David has provided the ultimate solution.
I don't know why there's a ";" in front of it.
That's (part of) my shell prompt. It's a convention originating in the
rc shell (although I learned of it from another); it pe
IME encoding is shown as
> application/octet-stream, using Neomutt's view command.
>
> Pressing Enter on the file name resulting in Geany (GUI text editor)
> being opened with the file. Nothing in my ~/.mailcap nor anything in
> /etc/mailcap mapped Geany to this MIME encodi
On Wed, Sep 15, 2021 at 09:34:50PM -0500, David Wright wrote:
[...]
> BTW, your shell command,
>
> !see --norun application/octet-stream:/dev/null
>
> will give you an answer in the context of a subshell, and
> not necessarily in the context of mutt itself [...]
Definitely, that's another po
Use mime.types to look up handlers for application/octet-stream. Can
# be undone with unmime_lookup.
mime_lookup application/octet-stream
That sends mutt looking in /etc/mime.types where it finds the line:
text/x-diff diff patch
Your attachment had the exte
* On 2021 15 Sep 14:20 -0500, to...@tuxteam.de wrote:
> On Wed, Sep 15, 2021 at 02:01:23PM -0400, Greg Wooledge wrote:
> > On Wed, Sep 15, 2021 at 12:58:10PM -0500, Nate Bargmann wrote:
> > > * On 2021 15 Sep 10:44 -0500, Jonathan Dowland wrote:
> > > > What does this command report?
> > > >
> > >
On Wed, Sep 15, 2021 at 02:01:23PM -0400, Greg Wooledge wrote:
> On Wed, Sep 15, 2021 at 12:58:10PM -0500, Nate Bargmann wrote:
> > * On 2021 15 Sep 10:44 -0500, Jonathan Dowland wrote:
> > > What does this command report?
> > >
> > > ;see --norun application/octet-stream:/dev/null
> Jonathan
e's a ";"
> in front of it.
Ahh! Thanks for that bit of info, Greg! I'll admit that is one command
I don't recall running across in 25 years of using Linux.
The man page synopsis:
run‐mailcap, view, see, edit, compose, print - execute programs via en‐
tries in the mailca
stead and that failed.
Jonathan's message confused me too. As far as I can tell, "see" is
a *shell* command, not a mutt command. I don't know why there's a ";"
in front of it.
unicorn:~$ see --norun application/octet-stream:/dev/null
Error: no "view" mai
* On 2021 15 Sep 10:44 -0500, Jonathan Dowland wrote:
> On Wed, Sep 15, 2021 at 08:37:51AM -0500, Nate Bargmann wrote:
> > application/octet-stream; vim %s; description=Patch file;
> > nametemplate=%s.patch
>
> application/octet-stream is a fairly generic mime type (and an odd
> choice for a text
On Wed, Sep 15, 2021 at 08:37:51AM -0500, Nate Bargmann wrote:
application/octet-stream; vim %s; description=Patch file; nametemplate=%s.patch
application/octet-stream is a fairly generic mime type (and an odd
choice for a text file, but so it goes). You may find vim is not a
suitable tool for
view command.
Pressing Enter on the file name resulting in Geany (GUI text editor)
being opened with the file. Nothing in my ~/.mailcap nor anything in
/etc/mailcap mapped Geany to this MIME encoding/file name.
As I hadn't been using Geany, I removed it and added the following line
to my
On Sun, Apr 05, 2020 at 11:05:28AM +0200, Beatrice Torracca wrote:
> On Sat April 4th tomás wrote:
>
> > Since
> > mutt takes posession of the screen, it seems best to direct
> > strace's output to a file and examine it later. Like so:
> >
> > strace -f -o my_trace_file -e trace=open,%process mu
On Sat April 4th tomás wrote:
> Since
> mutt takes posession of the screen, it seems best to direct
> strace's output to a file and examine it later. Like so:
>
> strace -f -o my_trace_file -e trace=open,%process mutt
Hi,
I tried that. Then I realized I have to apologize.
My first try with m
On Sb, 04 apr 20, 14:43:24, Beatrice Torracca wrote:
> Hello,
>
> I have been trying to make mutt open pdf files from the
> view-attachment dialog.
>
> I am using a Debian buster (Linux beapc 4.19.0-8-amd64 #1 SMP Debian
> 4.19.98-1 (2020-01-26) x86_64 GNU/Linux) with Mutt 1.10.1
> (2018-07-13).
e command "update-mime" that gave no error
> messages. Now in my /etc/mailcap file the first entry is
>
> application/pdf; evince %s; test=test -n "$DISPLAY"
>
> In my /etc/mime.types I have a line entry for pdf like this
>
> application/pdf
nux) with Mutt 1.10.1
> (2018-07-13).
Following your detailed description I'd expect it to work.
The only idea I can offer at the moment (and that's what
I'd try) is to run vim under strace to watch it trying
to open the mailcap and perhaps to exec evince. Since
mutt takes po
root) the command "update-mime" that gave no error
messages. Now in my /etc/mailcap file the first entry is
application/pdf; evince %s; test=test -n "$DISPLAY"
In my /etc/mime.types I have a line entry for pdf like this
application/pdf pdf
also sprach Nicolas George [2015-07-09 15:10 +0200]:
> > Does anyone know of a trick to just tell xdg-open to get out of the
> > way?
>
> Not using it? There is some information missing in your message.
I am talking about tools like gscan2pdf and others that hard-code
xdg-open to preview files.
Le primidi 21 messidor, an CCXXIII, martin f krafft a écrit :
> Does anyone know of a trick to just tell xdg-open to get out of the
> way?
Not using it? There is some information missing in your message.
Regards,
--
Nicolas George
signature.asc
Description: Digital signature
Hey,
run-mailcap worked for me for years. For a while already, xdg-open
is being pushed, using .desktop files to direct what to do with URIs
and files.
I really don't want this. I don't want .desktop files and I don't
want to have to create underdocumented ini-style configuration
On Thu,19.Nov.09, 17:20:34, Rick Pasotto wrote:
> Mutt is no longer invoking links for text/html messages. All I get is a
> text dump of the raw html.
>
> My ~/.muttrc file has these lines:
>
> set implicit_autoview=yes
> set mailcap_path="~/.mailcap:/etc/mailcap&qu
s needed?
I can't really help you with links, but I am very happy with the
following in my mailcap:
text/html; w3m -I %{charset} -T text/html -dump; copiousoutput
--
.''`. Wolodja Wentland
: :' :
`. `'` 4096R/CAF14EFC
`- 081C B7CD FF04 2
On Thu, Nov 19, 2009 at 05:20:34PM EST, Rick Pasotto wrote:
> Mutt is no longer invoking links for text/html messages. All I get is a
> text dump of the raw html.
>
> My ~/.muttrc file has these lines:
>
> set implicit_autoview=yes
> set mailcap_path="~/.mailcap:/etc/m
Mutt is no longer invoking links for text/html messages. All I get is a
text dump of the raw html.
My ~/.muttrc file has these lines:
set implicit_autoview=yes
set mailcap_path="~/.mailcap:/etc/mailcap"
My ~/.mailcap file has this line:
text/html; /usr/bin/links '%s&
--borders=no $1
j...@localhost:~$ print ./lists/biglots.txt
Error: no "print" mailcap rules found for type "text/plain"
j...@localhost:~$ exit
exit
Script done on Sun 02 Aug 2009 06:07:28 AM EDT
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a sub
On Sun, Jun 21, 2009 at 03:53:58AM EDT, Bob Proulx wrote:
> Chris Jones wrote:
[..]
> > Now on "lenny" although as far as I know I am using the same .muttrc and
> > the same /etc/mailcap that I copied over from the "etch" system, what
> > happens is that
Chris Jones wrote:
> Since obviously I run mutt in a terminal, a gnu/screen window actually,
> urlview would correctly launch the ELinks browser in the same terminal.
>
> Now on "lenny" although as far as I know I am using the same .muttrc and
> the same /etc/mailcap th
On Sat, Jun 13, 2009 at 01:10:13PM EDT, Chris Jones wrote:
> - Forwarded message from Tony Baldwin -
>
> Date: Sat, 13 Jun 2009 13:51:15 -0400
> From: Tony Baldwin
> To: Chris Jones
> Subject: Re: gnu/screen + mutt - mailcap creates a new terminal instance
>
- Forwarded message from Tony Baldwin -
Date: Sat, 13 Jun 2009 13:51:15 -0400
From: Tony Baldwin
To: Chris Jones
Subject: Re: gnu/screen + mutt - mailcap creates a new terminal instance
Chris Jones wrote:
> When I needed to view an url embedded in an e-mail, I would hit CTRL-B
>
ly launch the ELinks browser in the same terminal.
Now on "lenny" although as far as I know I am using the same .muttrc and
the same /etc/mailcap that I copied over from the "etch" system, what
happens is that urlview creates a new xterm where it then launches an
ELinks session.
W
1 - 100 of 156 matches
Mail list logo
