On 10/19/18 8:48 PM, Richard Kimberly Heck wrote:
On 10/19/18 3:46 PM, Paul A. Rubin wrote:
On 10/18/18 9:53 PM, Richard Kimberly Heck wrote:
On 10/18/18 2:01 PM, Paul A. Rubin wrote:
On 10/17/18 7:09 PM, Richard Kimberly Heck wrote:
On 10/17/18 2:35 PM, Paul A. Rubin wrote:
On 10/17/18 11:2
On 10/19/18 3:46 PM, Paul A. Rubin wrote:
> On 10/18/18 9:53 PM, Richard Kimberly Heck wrote:
>> On 10/18/18 2:01 PM, Paul A. Rubin wrote:
>>> On 10/17/18 7:09 PM, Richard Kimberly Heck wrote:
On 10/17/18 2:35 PM, Paul A. Rubin wrote:
> On 10/17/18 11:24 AM, Richard Kimberly Heck wrote:
>>
On 10/18/18 9:53 PM, Richard Kimberly Heck wrote:
On 10/18/18 2:01 PM, Paul A. Rubin wrote:
On 10/17/18 7:09 PM, Richard Kimberly Heck wrote:
On 10/17/18 2:35 PM, Paul A. Rubin wrote:
On 10/17/18 11:24 AM, Richard Kimberly Heck wrote:
On 10/17/18 9:30 AM, Paul A. Rubin wrote:
On 10/16/18 10:
On 10/18/18 2:01 PM, Paul A. Rubin wrote:
> On 10/17/18 7:09 PM, Richard Kimberly Heck wrote:
>> On 10/17/18 2:35 PM, Paul A. Rubin wrote:
>>> On 10/17/18 11:24 AM, Richard Kimberly Heck wrote:
On 10/17/18 9:30 AM, Paul A. Rubin wrote:
> On 10/16/18 10:24 PM, Andrew Parsloe wrote:
>> O
On 10/17/18 7:09 PM, Richard Kimberly Heck wrote:
On 10/17/18 2:35 PM, Paul A. Rubin wrote:
On 10/17/18 11:24 AM, Richard Kimberly Heck wrote:
On 10/17/18 9:30 AM, Paul A. Rubin wrote:
On 10/16/18 10:24 PM, Andrew Parsloe wrote:
On 17/10/2018 4:47 a.m., Paul A. Rubin wrote:
Dear devs,
I'm s
On 10/17/18 7:09 PM, Richard Kimberly Heck wrote:
On 10/17/18 2:35 PM, Paul A. Rubin wrote:
On 10/17/18 11:24 AM, Richard Kimberly Heck wrote:
On 10/17/18 9:30 AM, Paul A. Rubin wrote:
On 10/16/18 10:24 PM, Andrew Parsloe wrote:
On 17/10/2018 4:47 a.m., Paul A. Rubin wrote:
Dear devs,
I'm s
On 10/17/18 2:35 PM, Paul A. Rubin wrote:
> On 10/17/18 11:24 AM, Richard Kimberly Heck wrote:
>> On 10/17/18 9:30 AM, Paul A. Rubin wrote:
>>> On 10/16/18 10:24 PM, Andrew Parsloe wrote:
On 17/10/2018 4:47 a.m., Paul A. Rubin wrote:
> Dear devs,
>
> I'm struggling to cobble togeth
On 10/17/18 11:24 AM, Richard Kimberly Heck wrote:
On 10/17/18 9:30 AM, Paul A. Rubin wrote:
On 10/16/18 10:24 PM, Andrew Parsloe wrote:
On 17/10/2018 4:47 a.m., Paul A. Rubin wrote:
Dear devs,
I'm struggling to cobble together a module supporting the
pseudocode features of the algorithmicx
On 10/17/18 9:30 AM, Paul A. Rubin wrote:
> On 10/16/18 10:24 PM, Andrew Parsloe wrote:
>> On 17/10/2018 4:47 a.m., Paul A. Rubin wrote:
>>> Dear devs,
>>>
>>> I'm struggling to cobble together a module supporting the pseudocode
>>> features of the algorithmicx package. As a disclaimer, I'm trying
On 10/16/18 10:24 PM, Andrew Parsloe wrote:
> On 17/10/2018 4:47 a.m., Paul A. Rubin wrote:
>> Dear devs,
>>
>> I'm struggling to cobble together a module supporting the pseudocode
>> features of the algorithmicx package. As a disclaimer, I'm trying to
>> avoid flex insets and stick to environments
On 10/16/18 10:24 PM, Andrew Parsloe wrote:
On 17/10/2018 4:47 a.m., Paul A. Rubin wrote:
Dear devs,
I'm struggling to cobble together a module supporting the pseudocode
features of the algorithmicx package. As a disclaimer, I'm trying to
avoid flex insets and stick to environments as much as
On 17/10/2018 4:47 a.m., Paul A. Rubin wrote:
Dear devs,
I'm struggling to cobble together a module supporting the pseudocode
features of the algorithmicx package. As a disclaimer, I'm trying to
avoid flex insets and stick to environments as much as possible,
because there's less mousery swit
Dear devs,
I'm struggling to cobble together a module supporting the pseudocode
features of the algorithmicx package. As a disclaimer, I'm trying to
avoid flex insets and stick to environments as much as possible, because
there's less mousery switching an environment than insert an inset.
Ri
13 matches
Mail list logo
