Re: Using Notepad++ for editing Quickbook
"Paul A. Bristow" <[email protected]>
| Newsgroups | gmane.comp.lib.boost.documentation |
|---|---|
| Message-ID | <[email protected]> |
> -----Original Message----- > From: [email protected] [mailto:[email protected]] On Behalf Of > Rene Rivera > Sent: Thursday, October 13, 2011 3:33 AM > To: [email protected] > Subject: Re: [Boost-docs] Using Notepad++ for editing Quickbook > > On 10/12/2011 9:22 AM, Paul A. Bristow wrote: > > Some of you may want to use Notepad++ for editing Quickbook files. > > Ah, OK.. But how do you get syntax highlighting for Quickbook files in Notepad++ ? RTFM ;-) http://weblogs.asp.net/jgalloway/archive/2006/11/25/creating-a-user-defined-language-in-notepad.aspx and several other descriptions Well you can get keywords AND either operators ([ ] brackets) OR comment [/ ...] but not both (until we get a bug fix release) using the User Defined Language feature. You can choose the keywords you want my keyword 1 list is article authors bibliography blurb book library chapter part appendix preface div qandaset reference set copyright license def endsect footnote id import include index important link note purpose quickbook reference section source-mode and for keywords 2 I have h1 h2 h3 h4 h5 [funcref funcref [classref [memberref [enumref [macroref [headerref [globalref but you may want to choose others? You can chose your personal taste for the colors and other features, font, size, style. You enable operators [ and ] OR the comments start [/ and comment end ] (you can do both but the comment currently does not show in the right color ;-( Chose "qbk" for the file type will 'associate' this language setting for Quickbook files in future. IMO It isn't worth trying to distribute a file for this because tastes vary so much (I'm often told mine is bad but I like it!). This works OK-ish for me - but I normally use the old-and-now-obscure TextPad which I like better. HTH Paul --- Paul A. Bristow, Prizet Farmhouse, Kendal LA8 8AB UK +44 1539 561830 07714330204 [email protected]