From: Jani Nikula <jani.nikula@intel.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
intel-gfx@lists.freedesktop.org,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [maintainer-tools PATCH 1/2] dim: Accept .mbox and .patch files as apply-branch optional argument.
Date: Thu, 17 Aug 2017 11:12:54 +0300 [thread overview]
Message-ID: <878tiia9yx.fsf@nikula.org> (raw)
In-Reply-To: <20170817075742.ypsrkle3yya5vghi@phenom.ffwll.local>
On Thu, 17 Aug 2017, Daniel Vetter <daniel@ffwll.ch> wrote:
> One thing we maybe could be doing is a more fancy aliasing feature, along
> the lines of git aliases, where you can do whatever you want. Then you
> could do a dim apply-curl alias which resolves to curl $arg | dim apply.
> Not sure how to implement that though ...
We *already* have a fancy aliasing feature. You can add arbitrary
subcommands of your own, and you can override existing subcommands. Try
this in your ~/.dimrc:
dim_my_fancy_list_aliases()
{
echo "Hello world!"
dim_list_aliases
}
dim_alias_list_aliases=my-fancy-list-aliases
This first part will give you a new "dim my-fancy-list-aliases"
subcommand, and the second part will use it for "dim list-aliases".
Go wild. ;)
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-08-17 8:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-16 18:13 [maintainer-tools PATCH 1/2] dim: Accept .mbox and .patch files as apply-branch optional argument Rodrigo Vivi
2017-08-16 18:13 ` [maintainer-tools PATCH 2/2] dim: Accept patchwork URLs " Rodrigo Vivi
2017-08-16 18:17 ` Rodrigo Vivi
2017-08-17 7:45 ` Jani Nikula
2017-08-17 16:18 ` Rodrigo Vivi
2017-08-17 16:49 ` Rodrigo Vivi
2017-08-17 7:37 ` Jani Nikula
2017-08-17 16:08 ` Rodrigo Vivi
2017-08-17 7:30 ` [maintainer-tools PATCH 1/2] dim: Accept .mbox and .patch files " Jani Nikula
2017-08-17 7:57 ` Daniel Vetter
2017-08-17 8:12 ` Jani Nikula [this message]
2017-08-17 8:40 ` Daniel Vetter
2017-08-17 16:24 ` Rodrigo Vivi
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=878tiia9yx.fsf@nikula.org \
--to=jani.nikula@intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=rodrigo.vivi@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.