On Thu, Dec 17, 2020 at 10:40 AM Saša Janiška wrote:
> On Thu, 17 Dec 2020 07:51:34 +0100
> Mikael Sundqvist wrote:
>
> > To set the color theme, click the blue button "Set color theme".
>
> So, this is the only thing which can be configured?
>
>
> Sincerely,
> Gour
>
> --
> Everyone is forced
On Thu, 17 Dec 2020 07:51:34 +0100
Mikael Sundqvist wrote:
> To set the color theme, click the blue button "Set color theme".
So, this is the only thing which can be configured?
Sincerely,
Gour
--
Everyone is forced to act helplessly according to the qualities
he has acquired from the modes
On Thu, Dec 17, 2020 at 7:28 AM Saša Janiška wrote:
> On Tue, 4 Aug 2020 14:38:05 +0200
> Mikael Sundqvist wrote:
>
> > To make a symlink worked well here, in the sense that I got a context
> > extension in vs code, and when opening a context file it was
> > recognized as such.
>
> I was able
On Tue, 4 Aug 2020 14:38:05 +0200
Mikael Sundqvist wrote:
> To make a symlink worked well here, in the sense that I got a context
> extension in vs code, and when opening a context file it was
> recognized as such.
I was able to install vscode extension by symlinking...
> I could go into
On Wed, 5 Aug 2020 22:07:53 +0200
Mikael Sundqvist wrote:
> * Since January, the editor supports a global tasks.json file (if I
> understood
> https://stackoverflow.com/questions/41046494/making-global-tasks-in-vs-code
> correctly).
Are those extensions only for VSCode or they should work with
On Wed, Aug 5, 2020 at 11:57 AM Jeong Dal wrote:
> Dear Mikael,
>
>
> 2) Is there a nice way to compile the tex file from
>
> within vs code? As of
> now, I opened a terminal and compiled from that, but that feels like the
> wrong way of doing it.
>
>
> For the first question, I don’t know
Dear Mikael,
> 2) Is there a nice way to compile the tex file from
> within vs code? As of
> now, I opened a terminal and compiled from that, but that feels like the
> wrong way of doing it.
For the first question, I don’t know either.
For the second question, I’d like to explain what I did for
On Thu, Jul 30, 2020 at 12:25 PM Henning Hraban Ramm wrote:
>
> > Am 30.07.2020 um 07:52 schrieb Jeong Dal :
> >
> > Dear Alasdair McAndrew,
> >
> > I am using vscode in iMac, so my setting may not work for you.
> >
> >
> >
> > 1. First, find files for vscode in your TeX folder.
> >
> > In my
> Am 30.07.2020 um 03:57 schrieb Alasdair McAndrew :
>
> Thanks again, I've fiddled with SciTE, but when I attempted to compile a
> context file, I was told that "texexec" wasn't in my path, so somehow,
> somewhere, I must have picked up an old version of the compile command.
> Also, there
> Am 30.07.2020 um 07:52 schrieb Jeong Dal :
>
> Dear Alasdair McAndrew,
>
> I am using vscode in iMac, so my setting may not work for you.
>
>
>
> 1. First, find files for vscode in your TeX folder.
>
> In my case,
>
>
Dear Alasdair McAndrew,
I am using vscode in iMac, so my setting may not work for you.
1. First, find files for vscode in your TeX folder.
In my case,
/ConTeXt-homefolder/tex/texmf-context/context/data/vacode/extensions/context/*.*
2. In a homefolder, there is a hidden folder “.vacode”.
Hi Alasdair,
i fiddled with SciTE some years ago and ended with a file
myproperties.properties in the programdata\scite directory.
In this file i set the fonts and my context command as follows:
# Codepages
# UTF-8
code.page=65001
output.code.page=65001
# Byte
# code.page=0
Thanks again, I've fiddled with SciTE, but when I attempted to compile a
context file, I was told that "texexec" wasn't in my path, so somehow,
somewhere, I must have picked up an old version of the compile command.
Also, there doesn't seem to be an easy way of getting SciTE to use a
monospaced
> Am 29.07.2020 um 14:19 schrieb Alasdair McAndrew :
>
> Thank you very much, but in fact that script file "vscode-context.cmd" really
> just contains the same command for installing extensions as I quoted above -
> and so produces the same errors. Maybe I'll go back to trying SciTe - I gave
Thank you very much, but in fact that script file "vscode-context.cmd"
really just contains the same command for installing extensions as I quoted
above - and so produces the same errors. Maybe I'll go back to trying
SciTe - I gave it a bit of a go, but wasn't successful. Of all the
information
On 7/28/2020 6:51 AM, Alasdair McAndrew wrote:
I am installing the Windows version of ConTeXt, which comes with a
VSCode extension, in
\tex\texmf-context\context\data\vscode\extensions
with instructions to run (from within the VSCode terminal):
code -- extensions-dir --
16 matches
Mail list logo
