From: "Ron Frazier (NTP)" <timekeepingntplist@c3energy.com>
To: NTP Questions List <questions@lists.ntp.org>,
Thumb-GPS List <thumbgps-devel@lists.bufferbloat.net>,
Time Nuts List <time-nuts@febo.com>
Subject: [Thumbgps-devel] Semi OT - TIP Use Vim to color code NTP.CONF
Date: Tue, 27 Mar 2012 10:45:43 -0400 [thread overview]
Message-ID: <4F71D297.9050301@c3energy.com> (raw)
Hi all,
Here's a neat trick I just discovered. If you like to put lots of
comments in NTP.CONF, as I do, it's sometimes a challenge to find where
the active lines are and where the comments are.
I just discovered that, if you use the VIM programmer's editor to edit
the file, all the comment lines are automatically color coded blue and
all the active lines are color coded black. This makes it very easy to
see the structure of the file. Not wishing to start a firestorm
discussion of editors, you could use any programmer's editor that
recognizes and color codes the lines with # as a comment. VIM is even
smart enough to recognize in line comments after an active command.
I've also extracted almost all my explanatory comments and put them in
special sections with two blank lines before and after like so:
#########################################################
### explanatory comments
### here's the theory of how the next commands work
### so on and so forth etc etc etc
#########################################################
That also makes it easier to read the file.
See the following:
http://dl.dropbox.com/u/9879631/vim%20sample%20image.png
http://dl.dropbox.com/u/9879631/ntp.conf-normal
VIM is available for almost any platform, including graphical versions,
which I prefer. The graphical version for Ubuntu is called gnome-vim or
is it vim-gnome in the repository, and gvim once it's installed. I have
no idea if it works with Unity.
http://www.vim.org/
Sincerely,
Ron
--
(PS - If you email me and don't get a quick response, don't be concerned.
I get about 300 emails per day from alternate energy mailing lists and
such. I don't always see new messages very quickly. If you need a
reply and have not heard from me in 1 - 2 weeks, send your message again.)
Ron Frazier
timekeepingdude AT c3energy.com
reply other threads:[~2012-03-27 14:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F71D297.9050301@c3energy.com \
--to=timekeepingntplist@c3energy.com \
--cc=questions@lists.ntp.org \
--cc=thumbgps-devel@lists.bufferbloat.net \
--cc=time-nuts@febo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox