ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: ntg-context@ntg.nl
Cc: Hans Hagen <j.hagen@freedom.nl>
Subject: [NTG-context] Re: How to easily comment out/uncomment multiple lines all at once?
Date: Sun, 27 Apr 2025 20:54:37 +0200	[thread overview]
Message-ID: <c6169f45-4b57-4aeb-b033-ce30a5801c8a@freedom.nl> (raw)
In-Reply-To: <431378854.1243657.1745779357147@mail.yahoo.com>

On 4/27/2025 8:42 PM, Joel via ntg-context wrote:
> I have a single *.tex file that I have setup, here's a simple minimal 
> example:
> 
> \define\macroA{This outputs some stuff.}
> 
> \define\macroB{\input knuth }
> 
> \define\macroC{This outputs other stuff.}
> 
> \define\macroD{This outputs other stuff.}
> 
> \define\macroE{This outputs other stuff.}
> 
> \define[2]\macroF{This is text #1 and #2.}
> 
> \define\macroG{This outputs other stuff.}
> 
> \define\macroH{This outputs other stuff.}
> 
> \starttext
> 
> \macroA
> %\macroB
> %\macroC
> %\macroD
> %\macroE
> 
> %%% some more code
> 
> \macroF{a}{b}
> \macroG
> \macroH
> 
> \stoptext
> 
> Normally, I will compile it as above, so only two of the macros actually 
> appear. But sometimes, for testing purposes, I want to make sure my code 
> is functioning good, so I will go an un-comment all of the macros, and 
> then compile, and it basically does a test, making sure all of the 
> macros in my code function perfectly. When testing, it looks like this:
> 
> \starttext
> 
> \macroA
> \macroB
> \macroC
> \macroD
> \macroE
> 
> %%% some more code
> 
> \macroF{a}{b}
> \macroG
> \macroH
> 
> \stoptext
> 
> 
> Because the actual file is quite large, commenting and un-commenting the 
> lines takes a long time, and can lead to mistakes. Is there any simpler 
> way to easily switch between the two versions?

Search for "modes" ...

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
        tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive  : https://github.com/contextgarden/context
wiki     : https://wiki.contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2025-04-27 18:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <431378854.1243657.1745779357147.ref@mail.yahoo.com>
2025-04-27 18:42 ` [NTG-context] " Joel via ntg-context
2025-04-27 18:54   ` Hans Hagen via ntg-context [this message]
2025-04-27 18:58   ` [NTG-context] " mf
2025-04-27 19:10   ` Pablo Rodriguez via ntg-context

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=c6169f45-4b57-4aeb-b033-ce30a5801c8a@freedom.nl \
    --to=ntg-context@ntg.nl \
    --cc=j.hagen@freedom.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).