[xmonad] [xmonad-contrib] XMonad.Prompt.Pass patch

[adam vogt]

Hello Ardumont,

I've pushed your Aug 29 patch.

Sorry about the months-long delay: it's not supposed to be this
difficult to get your code into contrib, and I hope we can be more
responsive in the future.

Regards,
Adam

On Wed, Sep 3, 2014 at 4:36 AM, ardumont <eniotna.t at gmail.com> wrote:
>
> Zev Weiss writes:
>
>> On Aug 30, 2014, at 4:19 AM, ardumont <eniotna.t at gmail.com> wrote:
>>
>>>> When people say things like "ed is the standard text editor", they're typically (hopefully, if they're using the term correctly) referring to actual, real standards, like SUS.  For example, here's the SUS entry for ed: http://pubs.opengroup.org/onlinepubs/9699919799/utilities/ed.html
>>>>
>>>
>>> ok, real standards, POSIX and all.
>>> Definitions aligned now.
>>>
>>> (See, it was apparent but not obvious at all to me ;)
>>>
>>>> If you (or anyone else) can point to a real standard that specifies
>>>> the inclusion and behavior of 'pass', I'll retract my statement --
>>>> though I sincerely doubt such a standard exists.
>>>
>>> Standard begins somewhere.
>>> Sometimes, standard emerges with use.
>>>
>>>> If you want to try get 'pass' into SUS, you can file a bug at http://www.austingroupbugs.net (I won't be holding my breath).
>>>>
>>>
>>> I am not the one requiring this.
>>> Furthermore, I checked requirements to contribute and I do not recall seeing one
>>> about this.
>>>
>>> So, if it's the main issue at hand, please, can someone update the
>>> requirements in the xmonad site?
>>>
>>
>> I don't think anyone's claimed that being officially standardized is a
>> requirement for anything as far as xmonad is concerned (I certainly
>> didn't mean to imply that).
>
> Ok.
>
>> I was just pointing out that the "standard" claim on the website of the program in question was quite a stretch, and didn't give me an impression of great clueful-ness on the part of its author(s).
>
> Ok! But it also drove you `to voice *your* from-the-sidelines
> preference that this patch *not* be applied`...
>
> Is it that much of a problem as to prevent a patch from being applied?
>
> Again, if the patch is applied, people who wants this could use it.
> Others who are not interested simply ignore it.
>
>>>> Might pass's contrib/ directory be another (better, in my opinion)
>>>> place to consider putting this code?
>>>
>>> I am sorry I did not understand this sentence.
>>> What's pass's contrib/ directory?
>>>
>>
>> I was referring to this: http://git.zx2c4.com/password-store/tree/contrib (contrib/ being where interoperability code with other stuff often lives in various projects' source trees).
>>
>
> Ok. I see now.
>
> But I am not interested to provide this to pass.
> As said before, I believe this could be extended to use with other
> password manager.
> It has better chance to be improved in xmonad-contrib than in pass.
>
> I also believe the use case is interesting enough to be integrated
> (otherwise, I would not have proposed it).
>
> Then again, as you said, neither of us are qualified to apply or dismiss the patch :D
>
> In any case, thanks for clarifying Zev.
>
>>
>> Zev
>
> Cheers,
> --
> @ardumont
> _______________________________________________
> xmonad mailing list
> xmonad at haskell.org
> http://www.haskell.org/mailman/listinfo/xmonad