Re: Auto completion and speech recognition

On Thursday, February 2, 2017 at 12:27:25 PM UTC-5, Edward K. Ream wrote: > > On Thu, Feb 2, 2017 at 9:29 AM, Eric S. Johansson > wrote: > > This is another one of those "The UI world looks different when you don't >> use your hands" moments. >> > > ​Wouldn't that be

Re: Warning: file contains @+middle sentinel

On Thu, Feb 2, 2017 at 1:19 PM, Largo84 wrote: > I got this error message from Leo reading several @files, should I be > worried about losing data? > ​@+middle sentinels are old. You are probably safe, but I would double check. Edward -- You received this message because

Re: find wrap ignored, goto-global-line wrong

On Thu, Feb 2, 2017 at 2:39 PM, nic cave-lynch wrote: > Thanks Edward > > The goto-global-line shows the same problem with a brand new leo file, so > it's nothing to do with old sentinels. Maybe it's just the way I use it: > using @ and @c for introductory discussion at the

Re: find wrap ignored, goto-global-line wrong

Thanks Edward The goto-global-line shows the same problem with a brand new leo file, so it's nothing to do with old sentinels. Maybe it's just the way I use it: using @ and @c for introductory discussion at the top of functions means I can end up with 60 or more sentinels in a file, which can

Warning: file contains @+middle sentinel

I got this error message from Leo reading several @files, should I be worried about losing data? Rob.. -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to

Re: TEX doc colors changed

On Thu, Feb 2, 2017 at 12:12 PM, Largo84 wrote: > OK, good to know, thanks! BTW, I added the new setting at your suggestion > and it's working again as before. > ​Thanks for the clarification. Edward -- You received this message because you are subscribed to the Google

Re: TEX doc colors changed

OK, good to know, thanks! BTW, I added the new setting at your suggestion and it's working again as before. Rob.. On Thursday, February 2, 2017 at 12:33:45 PM UTC-5, Edward K. Ream wrote: > > On Thu, Feb 2, 2017 at 11:24 AM, Largo84 > wrote: > > Does this screen

Re: TEX doc colors changed

On Thu, Feb 2, 2017 at 11:24 AM, Largo84 wrote: Does this screen shot help? > > > > ​Yes. Thanks. ​ ​ This is what I would expect

Re: Auto completion and speech recognition

On Thu, Feb 2, 2017 at 9:29 AM, Eric S. Johansson wrote: This is another one of those "The UI world looks different when you don't > use your hands" moments. > ​Wouldn't that be nice. Me, I'm waiting for an eye-tracker tool... if I wanted to create an instance of

Re: TEX doc colors changed

Does this screen shot help? On Thursday, February 2, 2017 at 12:09:27 PM UTC-5, Edward K. Ream wrote: > > On Thu, Feb 2, 2017 at 10:49 AM, Largo84

Re: Problems with using NaturallySpeaking

​​ On Thu, Feb 2, 2017 at 9:19 AM, Eric S. Johansson wrote: is it possible to keep the node/section text focus active while I'm using > dictation box? > ​Yes, but it will be tricky. The minibuffer must preserve and *show* the selected text when it receives focus. For

Re: TEX doc colors changed

On Thu, Feb 2, 2017 at 10:49 AM, Largo84 wrote: why would the text color be different for comments after the stock TEX > comment character (%) than for after @ block? > ​I have no idea ;-) I would have to see the actual text. Edward -- You received this message because

Re: TEX doc colors changed

On Thu, Feb 2, 2017 at 10:45 AM, Edward K. Ream wrote: ​ ​>> ​ My preference is to keep the red text for comments following @, but don't know how to get that back. ​> ​ This will involve a new setting. I do this immediately. ​Done at 2b95b7d. The new setting is @bool

Re: TEX doc colors changed

Great, thanks! Just curious, though; why would the text color be different for comments after the stock TEX comment character (%) than for after @ block? On Thursday, February 2, 2017 at 11:45:54 AM UTC-5, Edward K. Ream wrote: > > On Thu, Feb 2, 2017 at 9:17 AM, Largo84 >

Re: TEX doc colors changed

On Thu, Feb 2, 2017 at 9:17 AM, Largo84 wrote: > I work with @language TEX a lot and now see that all doc parts after @ are > black text, not red as before. If I use the stock TEX comment character > (%), the following text is red as before and as expected. > > I see there has

Auto completion and speech recognition

This is another one of those "The UI world looks different when you don't use your hands" moments. The part of understanding this is to take a look at a tool I wrote called "togglename". Many moons ago I created a togglename demo video. It's not very good quality and really need some editing

Problems with using NaturallySpeaking

I have a problem my hands, and I use speech recognition. NaturallySpeaking doesn't deal well with QT widgets. Not your problem, but I'm trying to find some workarounds. Nuance uses something called "dictation box" which takes a region that is selected via a clipboard copy and puts it in a

TEX doc colors changed

I work with @language TEX a lot and now see that all doc parts after @ are black text, not red as before. If I use the stock TEX comment character (%), the following text is red as before and as expected. I see there has been much work recently on the colorizers so I don't know if this issue

Re: Leo now colorizes all @ and @doc parts as reStructuredText

On Thursday, February 2, 2017 at 6:08:53 AM UTC-5, Edward K. Ream wrote: > > This is a super improvement. How did we ever live without it? > > um, you're welcome? :-) -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this

Leo now colorizes all @ and @doc parts as reStructuredText

This is a super improvement. How did we ever live without it? Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To

Re: starting with leo writing literate python

On Thu, Feb 2, 2017 at 4:19 AM, Edward K. Ream wrote: It may be possible to colorize all doc parts using reStructuredText. I'll > look into this today. > ​Done in master at 66b8533. This is a super improvement to Leo. Edward -- You received this message because you are

Re: starting with leo writing literate python

On Thu, Feb 2, 2017 at 1:09 AM, Eric S. Johansson wrote: > back way too many years ago I started literate programming with cweb. I'm > returning to LP using leo but either I'm missing a feature or the approach > has changed. back in cweb days I wrote each section with a

starting with leo writing literate python

back way too many years ago I started literate programming with cweb. I'm returning to LP using leo but either I'm missing a feature or the approach has changed. back in cweb days I wrote each section with a narrative and then a code section. I've started importing an existing bit of code