When I go$ echo *I get a directory listing.
When I go$ echo * *I get a directory listing, followed by a second identical directory listing.
When I go$ echo **I only get one directory listing. What happens to the second asterisk in this case? Why doesn't it expand? I haven't been able to sleep... (2 Replies)
Hi all,
I had a typical problem.
I am using a parameter
PK="PK1 PK2 PK3"
i need to build the string
a.PK1=b.PK1 and a.PK2=b.PK2 and a.PK3=b.PK3
Please help (8 Replies)
I am attempting to find all complete words which contain an asterisk at the beginning and the end - for instance, "*Hello?*" or "*you*".
From what I've read, I would have thought that the following expression would do that just fine:
\<\*.*\*\>
\< denoting the beginning of a word.
\*... (12 Replies)
#! /bin/csh
set delimiter = |
foreach i (*)
set str_deli="$i$delimiter"
question: how to retain the value of str_deli so i can build a pipe delimited string?
end (1 Reply)
I need to replace occurrences of twelve asterisks "************" with the string " 0000000.00" . Note that there are two spaces in front of the first zero. How can I do this using awk or sed? (3 Replies)
Hi All,
I have a text file which is currently formatted like this:
TEXT1
***
TEXT2
***
TEXT3
***
I want text before *** to go into separate files. For example,
1.dat
TEXT1 (5 Replies)
Hi,
So I downloaded this kernel source and was able to build it successfully.
But I want to add this SDK source code inside, can anyone help me how to do this? Note that the SDK source can be built by itself.
I added the SDK in the main Makefile:
init-y := init/
#added SDK... (0 Replies)
I have data file that has this in it:
data.txt
.........
.........
PPJ97**2017PPJ97**2017-03-21-13.35.15.887208********************START ERROR LOGGING******************
PPJ97**2017-03-21-13.35.15.887208** PROMPT APPLICATION ERROR **
PPJ97**2017-03-21-13.35.15.887208** IN TIMESTAMP |... (1 Reply)
Note: **Showing Asterisks when using SUDO is not what I am looking for. That method is well documented**
Short Description: We have a requirement where users want to see that they are typing a password when logging into a RedHat box or when they are changing their password -- instead of... (1 Reply)
i need to replace all occurrences of "period asterisk" as it is shown in this:
blah blah .*:.*:.* blah blah
with:
::
so that the end result looks like this:
blah blah :: blah blah
I tried different variations of the following but it didint work:
%s_ .*:.*:.* _ :: _g (2 Replies)
Discussion started by: SkySmart
2 Replies
LEARN ABOUT REDHAT
code
code(n) [incr Tcl] code(n)
NAME
code - capture the namespace context for a code fragment
SYNOPSIS
code ?-namespace name? command ?arg arg ...?
DESCRIPTION
Creates a scoped value for the specified command and its associated arg arguments. A scoped value is a list with three elements: the
"@scope" keyword, a namespace context, and a value string. For example, the command namespace foo {
code puts "Hello World!" } produces the scoped value: @scope ::foo {puts {Hello World!}} Note that the code command captures the cur-
rent namespace context. If the -namespace flag is specified, then the current context is ignored, and the name string is used as the
namespace context.
Extensions like Tk execute ordinary code fragments in the global namespace. A scoped value captures a code fragment together with its
namespace context in a way that allows it to be executed properly later. It is needed, for example, to wrap up code fragments when a Tk
widget is used within a namespace: namespace foo {
private proc report {mesg} {
puts "click: $mesg"
}
button .b1 -text "Push Me" -command [code report "Hello World!"]
pack .b1 } The code fragment associated with button .b1 only makes sense in the context of namespace "foo". Furthermore, the "report"
procedure is private, and can only be accessed within that namespace. The code command wraps up the code fragment in a way that allows it
to be executed properly when the button is pressed.
Also, note that the code command preserves the integrity of arguments on the command line. This makes it a natural replacement for the
list command, which is often used to format Tcl code fragments. In other words, instead of using the list command like this: after 1000
[list puts "Hello $name!"] use the code command like this: after 1000 [code puts "Hello $name!"] This not only formats the command cor-
rectly, but also captures its namespace context.
Scoped commands can be invoked like ordinary code fragments, with or without the eval command. For example, the following statements work
properly: set cmd {@scope ::foo .b1} $cmd configure -background red
set opts {-bg blue -fg white} eval $cmd configure $opts Note that scoped commands by-pass the usual protection mechanisms; the command:
@scope ::foo {report {Hello World!}} can be used to access the "foo::report" proc from any namespace context, even though it is private.
KEYWORDS
scope, callback, namespace, public, protected, private
itcl 3.0 code(n)