On 10/23/2018 02:58 PM, dmccunney wrote:
> Their response was to implement provisions of the DKIP specifications.
> One requires email to be digitally signed to prove it's from who it
> says it's from. Another requires that email not be *changed* en
> route. This *breaks* mailing lists, because
On Tue, Oct 23, 2018 at 3:26 PM Kevin Spiteri wrote:
>>
>> > Have you tried the "Never send it to spam" gmail filter action?
>>
>> I didn't know there was one? Hmmm... didn't find it when I was fishing Nick
>> Kralevich's message out of the spam filter. (Somewhere under gear->configure
>> account
>
> > Have you tried the "Never send it to spam" gmail filter action?
>
> I didn't know there was one? Hmmm... didn't find it when I was fishing Nick
> Kralevich's message out of the spam filter. (Somewhere under
> gear->configure
> account maybe? I've always been reluctant to touch that stuff,
On Mon, Oct 22, 2018 at 1:31 PM Rob Landley wrote:
>
>
>
> On 10/22/2018 02:04 PM, enh wrote:
> > On Thu, Oct 18, 2018 at 11:59 AM Rob Landley wrote:
> >> Most commands never _stop_ accepting flags:
> >>
> >> ls file file file -l
> >> rm file file file -i
> >
> > interesting. in my mental
On 10/22/2018 02:04 PM, enh wrote:
> On Thu, Oct 18, 2018 at 11:59 AM Rob Landley wrote:
>> Most commands never _stop_ accepting flags:
>>
>> ls file file file -l
>> rm file file file -i
>
> interesting. in my mental model, i always assume "guideline 9"
>
On 10/18/2018 01:27 PM, Kevin Spiteri wrote:
> Sorry for the delay, everything you wrote yesterday wound up in gmail's
> spam
> filter again.
>
> Have you tried the "Never send it to spam" gmail filter action?
I didn't know there was one? Hmmm... didn't find it when I was fishing Nick
On Thu, Oct 18, 2018 at 11:59 AM Rob Landley wrote:
>
> On 10/18/2018 01:12 PM, enh wrote:
> > Yeah, my assumption was that as long as I'm still in the flags, --help
> > should
> > work. (But not *anywhere*.)
>
> Most commands never _stop_ accepting flags:
>
> ls file file file -l
> rm file
On Thu, Oct 18, 2018 at 11:59 AM Rob Landley wrote:
>
> On 10/18/2018 01:12 PM, enh wrote:
> > Yeah, my assumption was that as long as I'm still in the flags, --help
> > should
> > work. (But not *anywhere*.)
>
> Most commands never _stop_ accepting flags:
>
> ls file file file -l
> rm file
On 10/18/2018 01:12 PM, enh wrote:
> Yeah, my assumption was that as long as I'm still in the flags, --help should
> work. (But not *anywhere*.)
Most commands never _stop_ accepting flags:
ls file file file -l
rm file file file -i
lib/args.c has ^ to stop at the first non-option argument,
>
> Sorry for the delay, everything you wrote yesterday wound up in gmail's
> spam
> filter again.
>
Have you tried the "Never send it to spam" gmail filter action?
___
Toybox mailing list
Toybox@lists.landley.net
Yeah, my assumption was that as long as I'm still in the flags, --help
should work. (But not *anywhere*.)
Personally, I often just add --help on the end of what I've already typed
if I get stuck.
For this specific case, I think in my ideal world, a flag that takes
arguments from a list should
Sorry for the delay, everything you wrote yesterday wound up in gmail's spam
filter again.
On 10/17/2018 04:51 PM, enh wrote:
> i wanted to check that the Android scheduler policy output wasn't
> broken by recent changes, but i can't remember what the -O option is
> called...
>
> # ps -A -O
>
12 matches
Mail list logo
