ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Jaroslav Hajtmar <hajtmar@gyza.cz>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Bug in wiki \doifsamestringselse vs \doifsamestringelse
Date: Tue, 25 Jul 2017 22:16:16 +0000	[thread overview]
Message-ID: <43D004AC-FB3F-4CE2-A7E8-163603C143A2@gyza.cz> (raw)
In-Reply-To: <1500930226.2522.92.camel@gmail.com>

Thanx for reply and for fixed too. 
Jaroslav Hajtmar


Dne 24.07.17 23:06, ntg-context za uživatele Henri <ntg-context-bounces@ntg.nl za uživatele henrimenke@gmail.com> napsal(a):

    On Mon, 2017-07-24 at 16:54 +0000, Jaroslav Hajtmar wrote:
    > Hello ConTeXist
    >  
    > I add wiki information. In wiki on page http://wiki.contextgarden.net/System_Macros/Branches_and_D
    > ecisions is bug (I think) in caption \doifsamestringselse,\doifsamestring,\doifnotsamestring.
    >  
    > Right information is \doifsamestringelse,\doifsamestring,\doifnotsamestring (without s in first
    > keyword).
    > Macro \doifsamestringselse not work.
    >  
    > Is there anybody, that fix this bug?
    
    It's just a simple typo.  I fixed it for you.  You can also fix things like this yourself by making
    an account on the wiki and editing the page.
    
    >  
    > Jaroslav Hajtmar
    >  
    >  
    >  
    > ___________________________________________________________________________________
    > 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://context.aanhet.net
    > archive  : https://bitbucket.org/phg/context-mirror/commits/
    > wiki     : http://contextgarden.net
    > ___________________________________________________________________________________
    ___________________________________________________________________________________
    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://context.aanhet.net
    archive  : https://bitbucket.org/phg/context-mirror/commits/
    wiki     : http://contextgarden.net
    ___________________________________________________________________________________

___________________________________________________________________________________
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

      reply	other threads:[~2017-07-25 22:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-24 16:54 Jaroslav Hajtmar
2017-07-24 21:03 ` Henri
2017-07-25 22:16   ` Jaroslav Hajtmar [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=43D004AC-FB3F-4CE2-A7E8-163603C143A2@gyza.cz \
    --to=hajtmar@gyza.cz \
    --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).