From: Jani Nikula <jani.nikula@intel.com>
To: Rodrigo Vivi <rodrigo.vivi@gmail.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
intel-gfx <intel-gfx@lists.freedesktop.org>,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [maintainer-tools PATCH] dim.rst: Document aliases extension on dimrc.
Date: Fri, 18 Aug 2017 10:09:10 +0300 [thread overview]
Message-ID: <87mv6x73op.fsf@intel.com> (raw)
In-Reply-To: <CABVU7+vpz5YrorWEQ3bXQn6oJV6oyqk-Wrs35kAzfsmJb7Xb1Q@mail.gmail.com>
On Thu, 17 Aug 2017, Rodrigo Vivi <rodrigo.vivi@gmail.com> wrote:
> On Thu, Aug 17, 2017 at 10:33 AM, Jani Nikula <jani.nikula@intel.com> wrote:
>> On Thu, 17 Aug 2017, Rodrigo Vivi <rodrigo.vivi@intel.com> wrote:
>>> On my own workflow I was missing a way to download mboxes
>>> directly from patchwork with the patchwork id. So my first
>>> reflex was to modify dim to fulfil my needs. However that
>>> was increasing dim in complexity and dependencies and leaving
>>> that messy.
>>>
>>> That was when Jani suggested me the dimrc extension with the
>>> example that is now part of this spec.
>>>
>>> That was clean and simple enough to understand, so Daniel
>>> suggested me to add it to the spec.
>>>
>>> For record let's put my final local solution that lays now on
>>> my own ~/.dimrc
>>>
>>> dim_pwaq()
>>> {
>>> if [ -n "$1" ]; then
>>> curl https://patchwork.freedesktop.org/patch/$1/mbox/ | dim_apply_queued
>>> else
>>> echo "Give me a patchwork id"
>>> fi
>>> }
>>>
>>> Cc: Jani Nikula <jani.nikula@intel.com>
>>> Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
>>> Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
>>> ---
>>> dim.rst | 16 ++++++++++++++++
>>> 1 file changed, 16 insertions(+)
>>>
>>> diff --git a/dim.rst b/dim.rst
>>> index 802c776e03f9..c6728d186554 100644
>>> --- a/dim.rst
>>> +++ b/dim.rst
>>> @@ -441,6 +441,22 @@ usage
>>> Short form usage help listing all subcommands. Run by default or if an unknown
>>> subcommand was passed on the cmdline.
>>>
>>> +ALIASES
>>> +=======
>>> +
>>> +Extending **dim** functionalities
>>> +---------------------------------
>>> +
>>> +It is possible to create your own dim helper and aliases by adding them to \$HOME/.dimrc
>>> +
>>> +dim_my_fancy_list_aliases()
>>> +{
>>> + echo "Hello world!"
>>> + dim_list_aliases
>>> +}
>>> +
>>> +dim_alias_list_aliases=my-fancy-list-aliases
>>> +
>>
>> Naughty, naughty:
>>
>> $ make check
>> shellcheck -e SC2001 -e SC2034 -e SC2046 -e SC2086 -e SC2115 -e SC2119 -e SC2120 -e SC2143 dim bash_completion
>> rst2man --strict --no-raw dim.rst >/dev/null
>> dim.rst:453: (INFO/1) Possible title underline, too short for the title.
>> Treating it as ordinary text because it's so short.
>> Exiting due to level-1 (INFO) system message.
>> Makefile:49: recipe for target 'mancheck' failed
>> make: *** [mancheck] Error 1
>
> hm... it seems I need to update my shellcheck package... what version
> do you use?
> here shellcheck complains in non-sense stuff and make check doesn't
> proceed to that point...
shellcheck v0.4.4 here
BR,
Jani.
>
>
>>
>>
>> BR,
>> Jani.
>>
>>
>>> ENVIRONMENT
>>> ===========
>>
>> --
>> Jani Nikula, Intel Open Source Technology Center
>> _______________________________________________
>> Intel-gfx mailing list
>> Intel-gfx@lists.freedesktop.org
>> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
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-18 7:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-17 17:15 [maintainer-tools PATCH] dim.rst: Document aliases extension on dimrc Rodrigo Vivi
2017-08-17 17:33 ` Jani Nikula
2017-08-17 18:12 ` Rodrigo Vivi
2017-08-18 7:09 ` Jani Nikula [this message]
2017-08-18 23:44 ` Rodrigo Vivi
2017-08-21 8:39 ` Jani Nikula
2017-08-21 20:23 ` Rodrigo Vivi
2017-08-22 7:12 ` Jani Nikula
2017-08-22 16:30 ` Rodrigo Vivi
2017-08-23 8:43 ` Jani Nikula
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=87mv6x73op.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=rodrigo.vivi@gmail.com \
--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.