From: Matthias Meulien <orontee@gmail.com>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: Eli Zaretskii <eliz@gnu.org>,
dmitry@gutov.dev, andrew@trop.in,
emacs-devel <emacs-devel@gnu.org>
Subject: Re: [PATCH] notifications: Don't expand-file-name app-icon.
Date: Wed, 26 Jul 2023 19:46:14 +0200 [thread overview]
Message-ID: <CAFEQCfCbM2HU6nrPoB_N7UeFcTKZoWNz65BoSjVifNV1RgBLcA@mail.gmail.com> (raw)
In-Reply-To: <87h6pq4xxq.fsf@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 1516 bytes --]
Thanks for the precision and sorry for confusion.
Matthias
Le mer. 26 juil. 2023, 15:14, Michael Albinus <michael.albinus@gmx.de> a
écrit :
> Matthias Meulien <orontee@gmail.com> writes:
>
> Hi Matthias,
>
> >> In that case, we _definitely_ must call expand-file-name, and using
> >> relative file names without that is asking for trouble.
> >
> > Why not try to be compliant with the called API? According to the
> > Desktop Notification specification the Notify method support image path
> > being file URIs or in a freedesktop.org-compliant icon theme (see
> >
> https://specifications.freedesktop.org/notification-spec/notification-spec-latest.html#icons-and-images
> ).
>
> Sending an image_path instead of app_icon as file:/// URL is just an
> implementation detail. The `notifications-notify' API supports
> the :image-path argument if users are willing to use it.
>
> :app-icon can still be either a file name or an icon name. We must
> distinguish relative file names from image names; that's what this
> thread is about. Alternatively, we could allow only icon names with the
> :app-icon argument, but this wouldn't be backward compatible.
>
> > Being able to specify an icon with its name name according to Icon
> > Naming Specification (see
> >
> https://specifications.freedesktop.org/icon-naming-spec/latest/ar01s04.html
> )
> > is useful since file path vary depending on the OS!
>
> This is not true for relative file names.
>
> Best regards, Michael.
>
[-- Attachment #2: Type: text/html, Size: 2298 bytes --]
next prev parent reply other threads:[~2023-07-26 17:46 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-24 8:39 [PATCH] notifications: Don't expand-file-name app-icon Andrew Tropin
2023-07-24 8:39 ` [PATCH v2] notifications: Allow to use Icon Naming Specification for app-icon Andrew Tropin
2023-07-24 12:35 ` [PATCH] notifications: Don't expand-file-name app-icon Eli Zaretskii
2023-07-25 4:39 ` Andrew Tropin
2023-07-25 12:01 ` Eli Zaretskii
2023-07-25 12:59 ` Dmitry Gutov
2023-07-25 13:41 ` Andrew Tropin
2023-07-25 14:05 ` Eli Zaretskii
2023-07-25 16:48 ` Dmitry Gutov
2023-07-25 17:40 ` Eli Zaretskii
2023-07-25 19:09 ` Michael Albinus
2023-07-25 19:18 ` Eli Zaretskii
2023-07-26 7:05 ` Michael Albinus
2023-07-26 11:16 ` Eli Zaretskii
2023-07-26 12:36 ` Matthias Meulien
2023-07-26 13:14 ` Michael Albinus
2023-07-26 17:46 ` Matthias Meulien [this message]
2023-07-25 13:48 ` Eli Zaretskii
2023-07-25 10:43 ` Michael Albinus
2023-07-25 12:51 ` Eli Zaretskii
2023-07-25 13:51 ` Andrew Tropin
2023-07-25 14:47 ` Michael Albinus
2023-07-26 6:47 ` Andrew Tropin
2023-07-26 7:13 ` Michael Albinus
2023-07-26 12:05 ` Andrew Tropin
2023-07-26 11:59 ` [PATCH v3] notifications: Allow to use Icon Naming Specification for app-icon Andrew Tropin
2023-07-26 15:23 ` Eli Zaretskii
2023-07-26 17:46 ` Michael Albinus
2023-07-27 8:38 ` Andrew Tropin
2023-07-27 8:03 ` [PATCH v4] " Andrew Tropin
2023-07-27 11:49 ` Michael Albinus
2023-07-27 12:43 ` Eli Zaretskii
2023-07-27 14:59 ` Michael Albinus
2023-07-28 5:23 ` Andrew Tropin
2023-07-28 7:24 ` Michael Albinus
2023-07-28 11:07 ` Eli Zaretskii
2023-07-28 11:15 ` Michael Albinus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAFEQCfCbM2HU6nrPoB_N7UeFcTKZoWNz65BoSjVifNV1RgBLcA@mail.gmail.com \
--to=orontee@gmail.com \
--cc=andrew@trop.in \
--cc=dmitry@gutov.dev \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=michael.albinus@gmx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).