zsh-users
 help / color / mirror / code / Atom feed
From: mathieu stumpf guntz <psychoslave@culture-libre.org>
To: Ray Andrews <rayandrews@eastlink.ca>, zsh-users@zsh.org
Subject: Re: Can zsh `else` reserved keyword command be aliased and the lexem itself be repurposed as `fi` keyword command?
Date: Sun, 31 Dec 2017 00:32:39 +0100	[thread overview]
Message-ID: <e7cbd841-841a-09bd-4a55-982ebc7df60f@culture-libre.org> (raw)
In-Reply-To: <9b45b0dd-e396-6a1a-9bad-487fec982624@eastlink.ca>

[-- Attachment #1: Type: text/plain, Size: 1014 bytes --]



Le 31/12/2017 à 00:06, Ray Andrews a écrit :
> On 30/12/17 02:23 PM, mathieu stumpf guntz wrote:
>>
>>> #define define "undefine"
>>>   #define undefine "define"
>>>   alias alias="this must surely be forbidden"
>>
>> There are only a few things that must be intepreted in a clearly 
>> defined consensual way for a very limited and well specified context.
>
> Do we have a list of these?
I guess there is a formal definition of the zsh grammar somewhere, like 
an EBNF or something. Then that is the consensus on top on which you can 
build anything that is not unparsable according to that grammar. And zsh 
most probably is TuringComplete so basically you might build anything 
with it, including a parser for an other programming language. But the 
important thing for the internationalisation research underlying this 
experimentation is "how much can you localise the programming interface 
in an integrated way, that is how much the localised version works (and 
bugs) as the non-localised version?"

  reply	other threads:[~2017-12-30 23:32 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-28 15:07 mathieu stumpf guntz
2017-12-28 15:19 ` mathieu stumpf guntz
2017-12-29  8:47   ` Bart Schaefer
2017-12-29 10:51     ` mathieu stumpf guntz
2017-12-29 19:15       ` Bart Schaefer
2017-12-29 19:29         ` mathieu stumpf guntz
2017-12-29 19:49           ` Bart Schaefer
2017-12-29 20:27             ` Ray Andrews
2017-12-29 23:45               ` Bart Schaefer
2017-12-30  1:07                 ` Bart Schaefer
2017-12-30  9:50                   ` mathieu stumpf guntz
2017-12-30 10:05                     ` Frank Terbeck
2017-12-30 17:22                   ` Ray Andrews
2017-12-30 22:06                     ` Bart Schaefer
2017-12-30 23:00                       ` Ray Andrews
2017-12-30 17:16                 ` Ray Andrews
2017-12-30 22:23                   ` mathieu stumpf guntz
2017-12-30 23:06                     ` Ray Andrews
2017-12-30 23:32                       ` mathieu stumpf guntz [this message]
2017-12-30  9:36               ` mathieu stumpf guntz
2017-12-30 17:39                 ` Ray Andrews
2017-12-29 22:59       ` Nikolay Aleksandrovich Pavlov (ZyX)
2017-12-29  8:38 ` Bart Schaefer
2017-12-29 10:24   ` mathieu stumpf guntz

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=e7cbd841-841a-09bd-4a55-982ebc7df60f@culture-libre.org \
    --to=psychoslave@culture-libre.org \
    --cc=rayandrews@eastlink.ca \
    --cc=zsh-users@zsh.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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).