ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Matija Šuklje" <matija.suklje@rutka.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: ConTeXt-ifying Kile
Date: Sat, 29 Dec 2007 21:14:55 +0100	[thread overview]
Message-ID: <200712292115.01581.matija.suklje@rutka.net> (raw)
In-Reply-To: <op.t33r8ghmnx1yh1@your-b27fb1c401>


[-- Attachment #1.1: Type: text/plain, Size: 1519 bytes --]

Dne sobota 29. decembra 2007 je Idris Samawi Hamid napisal(a):
> Attached is the text file I use for Notepad++. It's (almost) complete and
> based on Hans' Scite files.

Hi, Idris!

Thanks :]
I'll need to add the brackets in myself, but that's the least I can do to give 
back to the ConTeXt community!

> I miss Kate and hope to check it out again whenever I get time to play
> with Linux again (it's been about four years).

Kate doesn't use the autocompletion itself, but if we manage to completely 
ConTeXt-ify Kile (which uses Kate), it will be one sweet ride :]

Dne sobota 29. decembra 2007 je Mojca Miklavec napisal(a):
> Do you know http://texshow.contextgarden.net/? (not that you can use
> it directly, but only to see ...)

No, I didn't. Thanks for the link :D Are there all the currently valid 
commands listed?

> Once you have the basic syntax ready: can you also convince the
> developers to support a list of what's allowed inside [options]?
> For example, it might be that only
>     \setupsomething[style=bold|italic|slanted|\command,strut=yes|no]
> is allowed.

From what I saw this is not yet implemented in Kile — not even for LaTeX or 
pure TeX. But the idea is really great, so I'll try my best to conveince 
them.


Cheers,
Matija

-- 
gsm: +386 41 849 552
e-mail: matija.suklje@rutka.net
www: http://matija.suklje.name

aim: hookofsilver
icq: 110183360
jabber/g-talk: matija.suklje@gabbler.org
msn: matija.suklje@rutka.net
yahoo: matija_suklje

[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 487 bytes --]

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2007-12-29 20:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-29 12:25 Matija Šuklje
2007-12-29 13:19 ` Mojca Miklavec
2007-12-29 13:30 ` Mojca Miklavec
2007-12-29 15:34 ` Idris Samawi Hamid
2007-12-29 20:14   ` Matija Šuklje [this message]
2007-12-29 20:40     ` Mojca Miklavec
2008-01-02 12:14   ` Matija Šuklje
2008-01-02 15:23     ` Idris Samawi Hamid
2008-01-03  0:15 ` Matija Šuklje
2008-01-03 13:14   ` Hans Hagen
2008-01-03 13:25     ` Idris Samawi Hamid

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=200712292115.01581.matija.suklje@rutka.net \
    --to=matija.suklje@rutka.net \
    --cc=ntg-context@ntg.nl \
    /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;
as well as URLs for NNTP newsgroup(s).