On Fri May 17, 2024 at 11:56 AM BST, Max Nikulin wrote:
> You may file an issue to the emacs bug tracker.
I didn't realise this was coming straight from upstream. If it were
a Debian-local issue, I'd file something, but I will respectfully
decline to engage with Emacs upstream.
(Interesting to
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
On 16/05/2024 14:48, Jonathan Dowland wrote:
On Wed May 15, 2024 at 4:51 PM BST, Max Nikulin wrote:
https://bugs.debian.org/1071036
update-mime does not escape semicolon in .desktop Exec entries
Re-reading your bug report I'm struck by how hard to reason about
(and test) the emacs .desktop
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
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 have filed
https://bugs.debian.org/1071036
update-mime does not escape semicolon
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=\\"\\$DISPLAY\\"
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+nmu1 all
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 question (one of the
On 2024-05-06 15:27, Greg Wooledge wrote:
On Mon, May 06, 2024 at 02:53:10PM +0200, Jesper Dybdal wrote:
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
On Mon, May 06, 2024 at 02:53:10PM +0200, Jesper Dybdal wrote:
> 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
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-handler/mailto:
14 matches
Mail list logo
