On 4/12/06, Nikolai Weibull <[EMAIL PROTECTED]> wrote:
> On 4/12/06, Yakov Lerner <[EMAIL PROTECTED]> wrote:
> > On 4/11/06, Nikolai Weibull <[EMAIL PROTECTED]> wrote:
> > > On 4/11/06, Yakov Lerner <[EMAIL PROTECTED]> wrote:
> > > > On 4/11/06, Nikolai Weibull <[EMAIL PROTECTED]> wrote:
> > > > > As per your request, here's a syntax/kconfig.vim.
> > > >
> > > > Nice job Nikolai, thanks.
> > > > I went though all 2.6 Kconfig files and noticed some mishighlightings.
> > > As a solution I've made a "light" version of the kconfig syntax to use
> > > as a default.  The "heavy" one previously defined can be enabled by
> > >
> > > :let g:kconfig_syntax_heavy = 1
> >
> > Light version suffers from this big problem: the apostrophe in help text
> > scrambles highlighting for many following paragpaphs
> > (like "won't" ). Heavy version doesn't suffer from this problem.
> >
> > Both in light and in heavy version: keywords (if, source )
> > are highlighted in help texts. Keywords probably shall not be highlighted
> > in help texts.
>
> OK, this and some syncing issues has been fixed.

Hi Nikolai,
Thanks for a great job. The apostrophe in helptexts mostly works.
I found two cases though where it does not work (see below),
Also, when helptext with apostrophe is top line of the
screen, all screen is painted same color (probably a syncing issue).
Thanks
Yakov
------------------------ case1 ------------------
config ARCNET_CAP
    tristate "Enable CAP mode packet interface"
    depends on ARCNET
    help
      ARCnet "cap mode" packet encapsulation. Used to get the hardware
          acknowledge back to userspace. After the initial protocol byte every
          packet is stuffed with an extra 4 byte "cookie" which doesn't
          actually appear on the network. After transmit the driver will send
          back a packet with protocol byte 0 containing the status of the
          transmition:
             0=no hardware acknowledge
             1=excessive nak
             2=transmition accepted by the reciever hardware

          Received packets are also stuffed with the extra 4 bytes but it will
          be random data.

          Cap only listens to protocol 1-8.
------------------------- case 2 ----------------------------------
# ARM925T
config CPU_ARM925T
    bool "Support ARM925T processor" if ARCH_OMAP1
    depends on ARCH_OMAP15XX
    default y if ARCH_OMAP15XX
    select CPU_32v4
    select CPU_ABRT_EV4T
    select CPU_CACHE_V4WT
    select CPU_CACHE_VIVT
    select CPU_COPY_V4WB
    select CPU_TLB_V4WBI
    help
      The ARM925T is a mix between the ARM920T and ARM926T, but with
      different instruction and data caches. It is used in TI's OMAP
      device family.

      Say Y if you want support for the ARM925T processor.
      Otherwise, say N.
----------------------------------------------------------------------------------------------

Reply via email to