From: Denis B. <dbi...@wa...> - 2012-05-24 16:19:37
|
Hi, would it be possible to add .ins in file extension filter? They are heavily used by package developers (and also by the "lettre" class users). -- Denis |
From: Tim H. <hof...@hi...> - 2012-05-24 16:51:15
|
> Von: Denis Bitouzé [mailto:dbi...@wa...] > Gesendet: Donnerstag, 24. Mai 2012 18:20 > > Hi, > > would it be possible to add .ins in file extension filter? They are heavily used by > package developers (and also by the "lettre" class users). Yes. Does it need any special formatting or is the same syntax as .tex? |
From: Denis B. <dbi...@wa...> - 2012-05-24 17:18:28
|
Le jeudi 24/05/12 à 18h51, "Tim Hoffmann" <hof...@hi...> a écrit : > Yes. Does it need any special formatting or is the same syntax > as .tex? In fact, I don't know as I didn't develop any package or class so far (but I'm planning to create a thesis class). Maybe Matthias could help for this. -- Denis |
From: Matthias P. <mat...@gm...> - 2012-05-24 20:06:18
|
Am 24.05.2012 18:51, schrieb Tim Hoffmann: >> Von: Denis Bitouzé [mailto:dbi...@wa...] >> Gesendet: Donnerstag, 24. Mai 2012 18:20 >> >> Hi, >> >> would it be possible to add .ins in file extension filter? They are > heavily used by >> package developers (and also by the "lettre" class users). > Yes. Does it need any special formatting or is the same syntax as .tex? It is a normal tex file. See the following lines for an example ----> % See file 'tablestyles.dtx' for copyright and licence. \input docstrip.tex \keepsilent \askforoverwritefalse \usedir{tex/latex/templatedemo} \preamble This is a generated file. Copyright (C) 2012 Matthias Pospiech ... This work has the LPPL maintenance status 'maintained'. This Current Maintainer of this work is Matthias Pospiech \endpreamble \generate{ \file{templatedemo.sty}{\from{templatedemo.dtx}{templatedemo.sty}} } \endbatchfile <---- |
From: Denis B. <dbi...@wa...> - 2012-05-29 18:02:54
|
Le jeudi 24/05/12 à 18h19, Denis Bitouzé <dbi...@wa...> a écrit : > would it be possible to add .ins in file extension filter? Also the .cfg extension is heavily used and, as .ins files, corresponding files use ordinary (La)TeX syntax. Would it possible to add it? -- Denis |
From: Tim H. <hof...@hi...> - 2012-05-29 22:33:47
|
> Von: Denis Bitouzé [mailto:dbi...@wa...] > Gesendet: Dienstag, 29. Mai 2012 20:03 > > Le jeudi 24/05/12 à 18h19, > Denis Bitouzé <dbi...@wa...> a écrit : > > > would it be possible to add .ins in file extension filter? > > Also the .cfg extension is heavily used and, as .ins files, corresponding files use > ordinary (La)TeX syntax. Added cfg and ins to the extension filter. Please check, if everything works with these files. |
From: Denis B. <dbi...@wa...> - 2012-05-30 07:54:12
|
Le mercredi 30/05/12 à 00h33, "Tim Hoffmann" <hof...@hi...> a écrit : > Added cfg and ins to the extension filter. Thanks! > Please check, if everything works with these files. .ins files are OK but .cfg are still (SVN 2898M) hidden. -- Denis |
From: Matthias P. <mat...@gm...> - 2012-05-30 19:55:45
|
Am 30.05.2012 00:33, schrieb Tim Hoffmann: > > Added cfg and ins to the extension filter. Please check, if everything works > with these files. > ins files have a limited range of commands. These could be automatically loaded for autocompletion. However I have not a list of these commands. I only copy them from other files... Matthias |
From: Denis B. <dbi...@wa...> - 2012-05-31 06:21:38
|
Le mercredi 30/05/12 à 21h55, Matthias Pospiech <mat...@gm...> a écrit : > ins files have a limited range of commands. These could be > automatically loaded for autocompletion. > > However I have not a list of these commands. I only copy them from > other files... I guess most of those commands are described in section 2 of dtxtut package/documentation and maybe DocStrip documentation. With TeX Live, you can easily reach them with: texdoc dtxtut texdoc DocStrip But this is an interesting question: for instance, biblatex.cfg is a file where the user can configure most of the biblatex options but currently TXS doesn't know biblatex's commands must be recognized in such a file (a commented \usepackage{biblatex} line doesn't help of course). Would it be possible, for instance with magic comments, to let TXS accept syntax from given class/packages in arbitrary files? -- Denis |