From: Thomas Wolff <towo@towo.net>
To: cygwin-apps@cygwin.com
Subject: Re: [PATCH mintty] Add an XWin XDG menu entry
Date: Wed, 08 Jul 2015 12:44:00 -0000 [thread overview]
Message-ID: <559D1B1C.5090103@towo.net> (raw)
In-Reply-To: <CAMKht8gWepBhE7+AUONa3VTnvf2Wo+P9jCnVkXzPjrMVNP5jQw@mail.gmail.com>
On 08.07.2015 01:40, Michael DePaulo wrote:
> On Tue, Jul 7, 2015 at 4:00 PM, Thomas Wolff <towo@towo.net> wrote:
>> Am 07.07.2015 um 13:47 schrieb Yaakov Selkowitz:
>>> On Tue, 2015-07-07 at 11:47 +0200, Thomas Wolff wrote:
>>>> On 07.07.2015 01:12, Yaakov Selkowitz wrote:
>>>>> ---
>>>>> Thomas, could you please ship a new release with this patch ASAP?
>>>> Are you sure this is desired? Mintty isn't related to X Windows;
>>> Well, not for a full X desktop, and that's the reason for the
>>> OnlyShowIn. But within the context of a multiwindow session it makes
>>> sense to provide this option.
>> OK, anyone else to approve this? Sorry I'm asking but some people might
>> think it's alien in an X menu.
>> (Would that addition actually pass without a mintty dependency on xdg?
>> Otherwise, since mintty is in cygwin-base, xdg itself could also include the
>> entry.)
>> Thomas
> I think this makes sense because:
> ...
Convinced. According to
file:///C:/cygwin/usr/share/doc/cygport/manual.html#robo164 ,
Categories and Additional_Fields parameters should be colon-separated,
so I would put:
make_desktop_entry mintty "Cygwin Terminal" utilities-terminal
"System:Terminal Emulator" "" "OnlyShowIn=X-Cygwin"
-- about the icon, shouldn't mintty's own icon be used here? How would
it be passed to cygport, does it need to be installed first?
Thomas
next prev parent reply other threads:[~2015-07-08 12:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-06 23:12 Yaakov Selkowitz
2015-07-07 9:47 ` Thomas Wolff
2015-07-07 11:47 ` Yaakov Selkowitz
2015-07-07 20:00 ` Thomas Wolff
2015-07-07 23:40 ` Michael DePaulo
2015-07-08 12:44 ` Thomas Wolff [this message]
2015-07-08 16:53 ` Yaakov Selkowitz
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=559D1B1C.5090103@towo.net \
--to=towo@towo.net \
--cc=cygwin-apps@cygwin.com \
/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.
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).