Wich Lua Editor For Mac
Hexinator allows you to store all assumptions and knowledge about a file format in so-called grammars while looking at a file. A grammar is an XML file that knows all structures and elements which may appear in a certain file format.
On Feb 23, 2018, at 12:37 PM, Dirk Laurie wrote: 2018-02-23 20:31 GMT+02:00 Francisco Olarte: On Fri, Feb 23, 2018 at 7:07 PM, Glenn Travis wrote: I see what you are saying, however, please note that on that page it reads Once you have built Lua, you may want to install it in an official place in your system. Now that is passive voice (may) and folks might skip or ignore that portion. Is 'passive voice' the correct term for these? English is not my native language, but I think I was taught 'User installs lua', active voice, 'Lua is installed by the user', passive voice ( similar to how it is in spanish, just asking, I really do not know ).
It's the subjunctive mode. Perfectly correct in this situation. Given that, I may I suggest that it be rewritten in active voice; you will need to install. You must install. I STRONGLY disagree with that. Many users DO NOT install lua from sources in an 'official' place, and in fact I've NEVER done it ( always installed it locally from sources, for 'official' installs i go the easy way and use package managers, I do not consider myself smart enough to install global packages from sources ).
And anyway, nothing in Lua is ever 'must'. Lua supplies tols, not policies. It was thus said that the Great Glenn Travis once stated: Howdy, It’s the same thing: Last login: Fri Feb 23 17:57:32 on ttys000 Glenns-iMac: trav$ cd /usr/local Glenns-iMac:local trav$ pwd /usr/local Glenns-iMac:local trav$ ll total 0 drwxr-xr-x 6 root wheel 192 Feb 23 16:44 bin drwxr-xr-x 4 root wheel 128 Jan 19 09:40 share drwxr-xr-x 3 root wheel 96 Feb 23 10:07 man drwxr-xr-x 2 root wheel 64 Feb 23 16:44 include drwxr-xr-x 2 root wheel 64 Feb 23 16:57 lib Glenns-iMac:local trav$ Well. It was thus said that the Great Glenn Travis once stated: Howdy, It’s the same thing: Last login: Fri Feb 23 17:57:32 on ttys000 Glenns-iMac: trav$ cd /usr/local Glenns-iMac:local trav$ pwd /usr/local Glenns-iMac:local trav$ ll total 0 drwxr-xr-x 6 root wheel 192 Feb 23 16:44 bin drwxr-xr-x 4 root wheel 128 Jan 19 09:40 share drwxr-xr-x 3 root wheel 96 Feb 23 10:07 man drwxr-xr-x 2 root wheel 64 Feb 23 16:44 include drwxr-xr-x 2 root wheel 64 Feb 23 16:57 lib Glenns-iMac:local trav$ Well. 2018-02-24 2:08 GMT+02:00 Glenn Travis: RE: readme.html I consider this to be technical writing and as such passive voice, may or should is absolutely wrong. It is hard to argue with someone that uses phrases like 'absolutely wrong'. Further, all that I am asking for is the addition of a few words to Mac users.
It is not a policy, they are instructions in which at times “must' is a requirement if one desires the user/reader to have success. Not even Windows gets separate treatment in readme.html. Why not have a go at a separate readme-osx.html? Mac users may^H^H^H must read it but others know they do not need to? On the other hand, even that may^H^H^H will be inadequate.
Lua Editor Download
Mac users are not in the habit of reading instructions. They are accustomed to things that Just Work. ('If you have a Mac oven, insert the dinner and press start. The oven will set itself and cook the dinner.' On Feb 23, 2018, at 9:36 PM, Dirk Laurie wrote: 2018-02-24 2:08 GMT+02:00 Glenn Travis: RE: readme.html I consider this to be technical writing and as such passive voice, may or should is absolutely wrong.
Perhaps it is due to a rather mindset that was developed as the supervisor of an operations technical writers group in a nuclear power plant back in the 80s. It is hard to argue with someone that uses phrases like 'absolutely wrong'. Further, all that I am asking for is the addition of a few words to Mac users.
It is not a policy, they are instructions in which at times “must' is a requirement if one desires the user/reader to have success. Seeing as how I don’t know Windows very well, perhaps make or make install as written in the readme.html page is all that is needed. I think that non-mac users can struggle with a five or six word heads up edit. Sean: On Fri, Feb 23, 2018 at 10:23 PM, Sean Conner wrote: Interesting. I have two Macs I use (one personal, one for work). On my personal one, '/usr/local' is owned by root, so I would get an error trying to install Lua. On the work Mac, however, '/usr/local' is owned by me (except for '/usr/local/man' for some reason).
The only thing I can think of is that I have used homebrew on the work Mac, but not on my personal Mac (I really don't do development on the home Mac). Who owns & which permissions does /usr have in those? ( i've seen this kind of strangeness in linux/bsd when someone install packages in some places, and related thingies when my su-happy colleagues create directories ) Francisco Olarte. Glenn: On Sat, Feb 24, 2018 at 12:36 AM, Glenn Travis wrote: The Sudo was a typo.
R, just confirming. I understand that 'make install' is a single command, but to get it on macOS correctly, one must use sudo make install. Interestingly enough until recently Mac Terminal commands, file names etc were not case sensitive IIRC the mac filesystem is case-insensitive.
To execute external commands the shells normally just looks for an executable file in $PATH, so they are going to find it. Some goes for file names, but do not goe to far with 'etc', as things like 'make' are case sensitive, and 'install' is not a fliename. BTW, I suspect Mac Terminal is equivalent to the xterm & clones I use in Linux.
In this case it does not execute commands, it executes a single one at start ( the shell, i think it's a bash clone in modern mac ) and it is the shell who execute commands. You can make it execute another thing. I just messed around with the make and the install commands. For instance, I could do make and then install (sudo install later).
Mmm, shocking. Maybe you have some 'install' alias/shell script somewhere, as install is normally just a fancy 'cp' program. I cannot find anything similar in my lua src tree using find.iname '.install.' To clarify it, in my machine: folarte@p:/tmp/lua-5.3.4$ type make install make is /usr/bin/make install is /usr/bin/install make and install are different programs, both provided by standard packages. Install is just a fancy copy. Without knowing what you have installed & the exact sequence of commands, it's neraly imposible to say more. Francisco Olarte.
Sean: On Fri, Feb 23, 2018 at 10:23 PM, Sean Conner wrote: Interesting. I have two Macs I use (one personal, one for work). On my personal one, '/usr/local' is owned by root, so I would get an error trying to install Lua. On the work Mac, however, '/usr/local' is owned by me (except for '/usr/local/man' for some reason). The only thing I can think of is that I have used homebrew on the work Mac, but not on my personal Mac (I really don't do development on the home Mac). Interesting.
Who owns & which permissions does /usr have in those? Sean: On Sat, Feb 24, 2018 at 11:11 PM, Sean Conner wrote: It was thus said that the Great Francisco Olarte once stated.
Interesting. Who owns & which permissions does /usr have in those? spcsaltmine-2:/usrll mmm, that 'll' seems to be used a lot in Mac. Is it an alias to 'ls -l'? If so, for this kind of things 'ls -la' is sometimes better ( as it includes the permisisons for /usr in.
-spc (So I own '/usr/local'. ) Yep, that you told before. I wanted to see which usr/group owns /usr and wich permissions it had. Anyway, seen the scary stuff npm has pulled around this week with the permissions, and the recomendations to chmod/own things in /usr I'm not too surprised to see that kid of stuff. I, personally, haven't touched the default permissions, everything owned by root in /usr /etc /bin /sbin for a couple decades, I've just get used to install things locally ( in ), but maybe bsd mac has different layout/conventions. Francisco Olarte. On Feb 25, 2018, at 12:06 PM, Francisco Olarte wrote: Sean: On Sat, Feb 24, 2018 at 11:11 PM, Sean Conner wrote: It was thus said that the Great Francisco Olarte once stated:.
Interesting. Who owns & which permissions does /usr have in those? spcsaltmine-2:/usrll mmm, that 'll' seems to be used a lot in Mac. Is it an alias to 'ls -l'? If so, for this kind of things 'ls -la' is sometimes better ( as it includes the permisisons for /usr in. -spc (So I own '/usr/local'.
) Yep, that you told before. I wanted to see which usr/group owns /usr and wich permissions it had. Anyway, seen the scary stuff npm has pulled around this week with the permissions, and the recomendations to chmod/own things in /usr I'm not too surprised to see that kid of stuff. I, personally, haven't touched the default permissions, everything owned by root in /usr /etc /bin /sbin for a couple decades, I've just get used to install things locally ( in ), but maybe bsd mac has different layout/conventions. Francisco Olarte. Sean: On Sat, Feb 24, 2018 at 11:11 PM, Sean Conner wrote: It was thus said that the Great Francisco Olarte once stated.
Who owns & which permissions does /usr have in those? spcsaltmine-2:/usrll mmm, that 'll' seems to be used a lot in Mac. Is it an alias to 'ls -l'? If so, for this kind of things 'ls -la' is sometimes better ( as it includes the permisisons for /usr in.spc (So I own '/usr/local'. ) Yep, that you told before. I wanted to see which usr/group owns /usr and wich permissions it had.
Anyway, seen the scary stuff npm has pulled around this week with the permissions, and the recomendations to chmod/own things in /usr I'm not too surprised to see that kid of stuff. I, personally, haven't touched the default permissions, everything owned by root in /usr /etc /bin /sbin for a couple decades, I've just get used to install things locally ( in ), but maybe bsd mac has different layout/conventions. Francisco Olarte.
You are so right about not knowing the OS/toolset very well, and I figure that; x8664-apple-darwin17 has a lot to do with it. I do not know why, but Darwin seems to be a collections of all sorts of unix like things; perhaps to get the macOS/ OS X GUI to work the way that they wanted it to. At this point, it seems to me that going the install via the terminal, Apple users have to use sudo make install to things working properly.
To be honest however, I can’t remember if I ever tried using the lua binaries route but perhaps that would explain how I ended up with version 5.1. I have the 3rd edition of Programming in Lua in which I am finding that 5.3 appears to be very different that 5.2 which is discussed in 3rd edition. Seeing as how the book is often over my head (I believe that the book description uses the word “programmer” which to me means experienced), I am having a debate with myself regarding spending money on the 4th edition.
The only programming experience that I have is in BASIC back in the mid 70s and that was on a HP 9830. On Fri, Feb 23, 2018 at 6:16 PM, Luiz Henrique de Figueiredo wrote: The README in the tarball and in says: Installing Lua Once you have built Lua, you may want to install it in an official place in your system.
In this case, do 'make install'. The official place and the way to install files are defined in the Makefile. You'll probably need the right permissions to install files.
Perhaps this should mention sudo? Given the previous section mentions unix-like and linux it may be useful, and maybe a mentioning mac os-x is unix like too ( I do not think linux users compiling will have problems, but mac users seem to be more like windows one, they do not know they OS/toolset too well ). Francisco Olarte. On Feb 27, 2018, at 10:03 AM, John Gabriele wrote: The 4th edition is of course updated for 5.3, but was also reorganized and now feels more like a tutorial than the previous edition. I bought the 3rd edition a ways back, didn't spend enough time with it, then recently bought the 4th ed and was glad I did.
it is probably off topic. I recently got PIL2 Page 139 has pseudo-code for lua require, which avoid infinite loops mod.lua: print(package.loaded.mod); require 'mod' Based on PIL2, required 'mod' should print true, and stop On lua 5.2.4 and 5.3.4, above code print bunch of nil, then crash.
Does PIL3 and PIL4 changed the require implentation? Read Lua 5.3 reference manual, but found nothing. I suppose that is true for the heavy users, but not all that sure about someone who pretty much lives in GUI and only wants to learn lua. Having never used Homebrew, I do not know what that process is all about.
Also, I would think that if whomever thinks that the use of sudo is dangerous changing ownership or permissions of a root owned directory path is even more so. Therefore, I would also think that the Unix heavy types would know all that kinda stuff and simply ignore the sudo make install.
On Tue, Feb 27, 2018 at 4:26 AM, Glenn Travis wrote: You are so right about not knowing the OS/toolset very well, and I figure that; x8664-apple-darwin17 has a lot to do with it. I do not know why, but Darwin seems to be a collections of all sorts of unix like things; perhaps to get the macOS/ OS X GUI to work the way that they wanted it to.
Hi Glen, All Unixes and unix-like systems are a little different because they.are. a collection of little tools. OSX has it's underpinnings from different sources than Linux due to licensing and Steve Jobs being, well, Steve Jobs. Anyway, what you'll find is in some cases it's much closer to BSD than GNU tools used in GNU/Linux (every 'Linux' except Android). I know that doesn't make a hill of beans difference to you right now but make no mistake: OSX is certified UNIX. GNU/Linux is not. OSX adheres to standards that 'Linux' does not.
At this point, it seems to me that going the install via the terminal, Apple users have to use sudo make install to things working properly. I'd like to point out that sudo is no different than having to type in your password before you install something from the app store or buy something with your paypal account. It is a means to prove credentials and elevate privilege in Unix. I'm not sure if this has been suggested, but you Lua can be run from within the src directory where it was built or be put pretty much.anywhere. that you have access. If you don't want to bother installing it system wide (which requires sudo!), then alter the makefile (that installs Lua) to point to your local home directory and install it there (/bin perhaps?). Then you add that path to your shell initialization and it's always available to YOU but it's not available to anyone else.
On a Mac Laptop or PC, that isn't really an issue I suspect. I'm sure if you ask, someone on the list can help out with the commands if you figure out what shell your using. Dirk can provide a link to that I think? (Also another joke, just Google it). To be honest however, I can’t remember if I ever tried using the lua binaries route but perhaps that would explain how I ended up with version 5.1. I have the 3rd edition of Programming in Lua in which I am finding that 5.3 appears to be very different that 5.2 which is discussed in 3rd edition.
Seeing as how the book is often over my head (I believe that the book description uses the word “programmer” which to me means experienced), I am having a debate with myself regarding spending money on the 4th edition. The only programming experience that I have is in BASIC back in the mid 70s and that was on a HP 9830.
Wich Lua Editor For Mac Free
It seems to me you are experiencing the same response that 99% of us do when faced with a new challenge. I've been using computers literally my whole life and I still.seethe. when doing something new. I want to throw my computer (I know, I need help) because they are so.
Keep persisting. Some advice since you didn't ask: - PIL 4 is a fantastic book. If you know what a loop and a variable is, start at Page 1 and follow the examples. Otherwise, learn what a loop and a variable is and then start at page 1.;) - Read some Unix history and start at the basics by learning to follow man pages (short for Manual because people in Unix hate typing. Tee hee, that's a joke.).
Man pages are also something that is.totally infuriating. until you 'get it' and then it's good. I find them easiest to read online, but have never looked for OSX man pages (I mostly use FreeBSD).
KEEP NOTES. Write down all your commands and come back to it and update it. Those notes will become invaluable and if you persist will likely turn into 'shell scripts'.
Follow KHMan's advice (pretty much the same as keep notes). Start a temp directory (mkdir /temp/) and dump your work in there until it's worth keeping.
As for GUIs, ZeroBrane is a fantastic way to learn Lua. There are a TON of great examples.
Geany and Scite are both good free GUI editors that support Lua syntax highlighting but don't support a Lua debugger out of the box. Hope that helps.:) Cheers, Russ. On Feb 23, 2018, at 11:49 AM, Francisco Olarte wrote: On Fri, Feb 23, 2018 at 6:16 PM, Luiz Henrique de Figueiredo wrote: The README in the tarball and in says: Installing Lua Once you have built Lua, you may want to install it in an official place in your system. In this case, do 'make install'. The official place and the way to install files are defined in the Makefile. You'll probably need the right permissions to install files.
Perhaps this should mention sudo? Given the previous section mentions unix-like and linux it may be useful, and maybe a mentioning mac os-x is unix like too ( I do not think linux users compiling will have problems, but mac users seem to be more like windows one, they do not know they OS/toolset too well ). Francisco Olarte.