10-21-2010
Just add the slash, becasue, I found it was not easier, it just saves you a byte of precious line space, you ingrate!
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hello
I am using Debain Potato and I changed the PS1. When I log in locally everythink is fine, except that when I enter a long row without hitting enter, then it word wraps automatically. And it does it not at the end of the row, it does it in the middle of the row!
It also does not writes... (7 Replies)
Discussion started by: Fwurm
7 Replies
2. UNIX for Advanced & Expert Users
I want to set my prompt to something more descriptive than a plain old $, so I set the PS1 variable as such:
PS1=""
Which changes the prompt correctly, but when I change directories, it does not update the prompt. So I tried this:
PS1="`pwd`>"
I get the same results when changing... (2 Replies)
Discussion started by: dangral
2 Replies
3. UNIX for Dummies Questions & Answers
can anyone tell me how to change the $ prompt by calling a variable.
Say for example i called a var 'enable' I and would like the $ prompt to change to a phrase like 'my prompt' any help would be great (1 Reply)
Discussion started by: pg080394
1 Replies
4. UNIX for Dummies Questions & Answers
I know this question has come up before but I couldn't find any documentation on ksh here.
I'm trying
PS1="`whoami`@`hostname`:`pwd`> "
export PS1
in ksh but the working directory sticks at the home directory. How do I fix that? Also, how do I make the prompt bold in korn? (3 Replies)
Discussion started by: rein
3 Replies
5. Shell Programming and Scripting
I want to change the PS1 prompt with current time.
I want the PS1 to update for every one second.
I write a Script.
PS1='\T'
but it updates after i press enter key.I want to update without pressing enter key.
can any one help me? (0 Replies)
Discussion started by: lakshmananindia
0 Replies
6. UNIX for Dummies Questions & Answers
please advise what's wrong with this command ?
PS1="`hostname`:`who am i | cut -d " " -f1`:>>"
trying to make the PS1 prompt look like :
machine_name:username:>>
thank you (4 Replies)
Discussion started by: venhart
4 Replies
7. Shell Programming and Scripting
I am 100% new to Unix and trying to learn.
This is my first time even touching a script in Unix.
We have the following variable script that I am trying to run....
##################################
###### variable test###
##################################
Hostname=`hostname`... (3 Replies)
Discussion started by: LRoberts
3 Replies
8. Shell Programming and Scripting
I have coded PS1 as shown, producing the following result when writing on the command line
┌─ cdl
└──╼ make tracepdf2d
If I make an error in the command an ✗ is printed
┌─ ✗ cdl
└──╼ ls-a
ls-a: command not found
My problem is that if I just press enter, I do not want to have the... (3 Replies)
Discussion started by: kristinu
3 Replies
9. Shell Programming and Scripting
I have searched through google, and this forum to try and find the answer, but alas, nothing quite hits the whole answer.
I am trying to read the last line (or lines) of some log files. I do this often.
The files are named sequentially, using the date as part of the file name, and appending... (18 Replies)
Discussion started by: BatterBits
18 Replies
10. UNIX for Dummies Questions & Answers
Hello I am attempting to generate a bash scrip that prompts me at loggin to change my PS1 -
However, I am running into an issue w/ the code.
#!/bin/bash
#the point of this script is to that it automates and changes my prompts every day
msg1="What do you feel like adding today :"
echo... (11 Replies)
Discussion started by: D'go
11 Replies
LEARN ABOUT DEBIAN
luac50
LUAC(1) General Commands Manual LUAC(1)
NAME
luac - Lua compiler
SYNOPSIS
luac [ options ] [ filenames ]
DESCRIPTION
luac is the Lua compiler. It translates programs written in the Lua programming language into binary files that can be latter loaded and
executed.
The main advantages of precompiling chunks are: faster loading, protecting source code from user changes, and off-line syntax checking.
Pre-compiling does not imply faster execution because in Lua chunks are always compiled into bytecodes before being executed. luac simply
allows those bytecodes to be saved in a file for later execution.
luac produces a single output file containing the bytecodes for all source files given. By default, the output file is named luac.out, but
you can change this with the -o option.
The binary files created by luac are portable to all architectures with the same word size. This means that binary files created on a
32-bit platform (such as Intel) can be read without change in another 32-bit platform (such as Sparc), even if the byte order (``endian-
ness'') is different. On the other hand, binary files created on a 16-bit platform cannot be read in a 32-bit platform, nor vice-versa.
In the command line, you can mix text files containing Lua source and binary files containing precompiled chunks. This is useful to com-
bine several precompiled chunks, even from different (but compatible) platforms, into a single precompiled chunk.
You can use - to indicate the standard input as a source file and -- to signal the end of options (that is, all remaining arguments will be
treated as files even if they start with -).
The internal format of the binary files produced by luac is likely to change when a new version of Lua is released. So, save the source
files of all Lua programs that you precompile.
OPTIONS
Options must be separate.
-l produce a listing of the compiled bytecode for Lua's virtual machine. Listing bytecodes is useful to learn about Lua's virtual
machine. If no files are given, then luac loads luac.out and lists its contents.
-o file
output to file, instead of the default luac.out. The output file may be a source file because all files are loaded before the out-
put file is written. Be careful not to overwrite precious files.
-p load files but do not generate any output file. Used mainly for syntax checking and for testing precompiled chunks: corrupted files
will probably generate errors when loaded. Lua always performs a thorough integrity test on precompiled chunks. Bytecode that
passes this test is completely safe, in the sense that it will not break the interpreter. However, there is no guarantee that such
code does anything sensible. (None can be given, because the halting problem is unsolvable.) If no files are given, then luac
loads luac.out and tests its contents. No messages are displayed if the file passes the integrity test.
-s strip debug information before writing the output file. This saves some space in very large chunks, but if errors occur when run-
ning these chunks, then the error messages may not contain the full information they usually do (line numbers and names of locals
are lost).
-v show version information.
FILES
luac.out default output file
SEE ALSO
lua(1)
http://www.lua.org/
DIAGNOSTICS
Error messages should be self explanatory.
AUTHORS
L. H. de Figueiredo, R. Ierusalimschy and W. Celes (lua@tecgraf.puc-rio.br)
2002/12/13 11:45:12 LUAC(1)