ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Andrea Valle <valle@di.unito.it>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: off-topic : about smultron
Date: Mon, 6 Oct 2008 23:30:57 +0200	[thread overview]
Message-ID: <5C0DF9EA-7DF2-4B2D-A5C0-41556F00CCC3@di.unito.it> (raw)
In-Reply-To: <2143F33F-0F22-478C-B75A-8CFF99EA7491@mac.com>


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

Dear Dalyoung,

Sorry,I don't know. The only thing I've noticed is that Smultron  
refreshes its result window after compilation is completed and not  
while compiling, I guess it's a matter of piping. So, sometimes there  
a relevant lag and I have to wait a bit in order to look at what has  
happened.

Best

-a-


On 6 Oct 2008, at 09:04, Dalyoung Jeong wrote:

> Dear all,
>
> I hope that you understand a little bit off topic question.
>
> Recently, I installed smultron and set it up to use ConTeXt Minimals
> following the instruction in ConTeXt wiki.
> Basically it worked.
> But the command result window didn't properly show what is going on
> during the compilation.
> But it appeared some time but it didn't some other time. I couldn't
> figure out when it did and when it didn't.
> Even in the case that it showed the result, it didn't refresh after I
> compiled the same file again.
>
> Does some one help me to fix it?
>
> Thank you.
>
> Best regards,
>
> Dalyoung
> ______________________________________________________________________ 
> _____________
> 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
> ______________________________________________________________________ 
> _____________

--------------------------------------------------
Andrea Valle
--------------------------------------------------
CIRMA - DAMS
Università degli Studi di Torino
--> http://www.cirma.unito.it/andrea/
--> http://www.myspace.com/andreavalle
--> andrea.valle@unito.it
--------------------------------------------------


"
Think of it as seasoning
. noise [salt] is boring
. F(blah) [food without salt] can be boring
. F(noise, blah) can be really tasty
"
(Ken Perlin on noise)






[-- Attachment #1.2: Type: text/html, Size: 9548 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:[~2008-10-06 21:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-06  7:04 Dalyoung Jeong
2008-10-06 21:30 ` Andrea Valle [this message]

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=5C0DF9EA-7DF2-4B2D-A5C0-41556F00CCC3@di.unito.it \
    --to=valle@di.unito.it \
    --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).