How do I make this mailman list send me only digest email and not all emails
please?
Kailash
> On Mar 1, 2016, at 1:17 PM, Alan Mead wrote:
>
> On 03/01/2016 01:44 AM, Friedrich Beckmann wrote:
>>
"This is a development version. It may contain bugs.“
>>
>> in the title bar? Would you c
On 03/01/2016 01:44 AM, Friedrich Beckmann wrote:
"This is a development version. It may contain bugs.“
in the title bar? Would you consider this non-scary?
What about having just
Friedrich
No, it doesn't seem scary to me; but I hope we continue to be open to
feedback from users. If a sn
> Am 01.03.2016 um 08:33 schrieb Alan Mead :
>
> On 02/29/2016 11:37 PM, John Darrington wrote:
>>
>> How about we implement Ben's suggestion AND have an abridged version of his
>> words
>> on the title-bar?
>>
>> The abridged version could read: "This is a development version. It may
>> cont
On 02/29/2016 11:37 PM, John Darrington wrote:
The wording seems find to me.
I'm not so sure that is will be as noticable as we would like - it will scroll
off the top of the screen after a large output. And in cases like reported
here:
https://lists.gnu.org/archive/html/pspp-users/2
On Sun, Feb 28, 2016 at 10:00:41AM -0800, Ben Pfaff wrote:
I suggest putting it into the output window at startup, once. This is
easy to do, it is likely that users will notice, and it is not as
obnoxious as some of the other options.
For example:
diff --
Doing it the way Ben suggests would not break the regression tests.
On Mon, Feb 29, 2016 at 07:41:10AM -0600, Alan Mead wrote:
On 2/28/2016 12:00 PM, Ben Pfaff wrote:
> I suggest putting it into the output window at startup, once. This is
> easy to do, it is likely that users will
I still think a lot of this can be avoided through better and clearer
messaging when downloading the software, but it is also a good idea to have
a message like this in the output, one time.
The suggested text had a few grammatical errors, though, so here are some
fixes:
This is a development
On 2/29/2016 10:01 AM, Ben Pfaff wrote:
> I don't see why the regression tests would break. For one thing, we
> don't have regression tests for the GUI, which seems to be mostly what
> we're talking about. Second, it would not be hard to disable this
> message for the regression tests (e.g. with --
On Mon, Feb 29, 2016 at 09:57:53AM -0600, Alan Mead wrote:
> On 2/28/2016 12:44 AM, John Darrington wrote:
> > 1. In the output window after each operation.
> >
> >I don't think that is a good idea for several reasons: a) It would
> >break all of our regression tests;
>
> I was referring t
On 2/28/2016 12:44 AM, John Darrington wrote:
> 1. In the output window after each operation.
>
>I don't think that is a good idea for several reasons: a) It would
>break all of our regression tests;
Ben,
I was referring to this. I assumed that John meant that all the
regression tests wou
On Mon, Feb 29, 2016 at 07:41:10AM -0600, Alan Mead wrote:
> On 2/28/2016 12:00 PM, Ben Pfaff wrote:
> > I suggest putting it into the output window at startup, once. This is
> > easy to do, it is likely that users will notice, and it is not as
> > obnoxious as some of the other options.
> > +
> >
On 2/28/2016 12:00 PM, Ben Pfaff wrote:
> I suggest putting it into the output window at startup, once. This is
> easy to do, it is likely that users will notice, and it is not as
> obnoxious as some of the other options.
> +
> + text_item_submit (
> +text_item_create (TEXT_ITEM_PARAGRAPH,
>
12 matches
Mail list logo
