01-09-2017
Corona688 is right - use the + repetition indicator instead of the * (which indicates zero or more repetitions).
This User Gave Thanks to RudiC For This Post:
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi
I have installed solaris 10 on an intel machine. Logged in as root. In CDE, i open terminal session, type login alex (normal user account) and password and i get this message
No utpmx entry: you must exec "login" from lowest level "shell" :confused:
What i want is: open various... (0 Replies)
Discussion started by: peterpan
0 Replies
2. UNIX for Advanced & Expert Users
Do someone know how to delete entry(some lines)
in file "wtmpx" that command "last" use it.
this file is binary so I cannot edit directy.
=========================
#last
root pts/1 noc Fri Mar 3 22:04 still logged in
root pts/1 noc Fri Mar 3 22:01 - 22:02 ... (4 Replies)
Discussion started by: arm_naja
4 Replies
3. Shell Programming and Scripting
Hi,
I've modified the syslogd source to include a thread that will keep track of a timer(or a timer thread). My intention is to check the file size of /var/log/messages in every one minute & if the size is more than 128KB, do a echo " " > /var/log/messages, so that the file size will be set... (7 Replies)
Discussion started by: jockey007
7 Replies
4. Solaris
When trying to open a document with VI editor, getting the following error..
E558: Terminal entry not found in terminfo
'vt100' not known. Available builtin terminals are:
builtin_gui
builtin_riscos
builtin_amiga
builtin_beos-ansi
builtin_ansi
builtin_pcansi
... (8 Replies)
Discussion started by: vikram3.r
8 Replies
5. Shell Programming and Scripting
Hi All,
I have working (Perl) code to combine 2 input files into a single output file using the join function that works to a point, but has the following limitations:
1. I am restrained to 2 input files only.
2. Only the "matched" fields are written out to the "matched" output file and... (1 Reply)
Discussion started by: Katabatic
1 Replies
6. Shell Programming and Scripting
Hi,
I have line in input file as below:
3G_CENTRAL;INDONESIA_(M)_TELKOMSEL;SPECIAL_WORLD_GRP_7_FA_2_TELKOMSEL
My expected output for line in the file must be :
"1-Radon1-cMOC_deg"|"LDIndex"|"3G_CENTRAL|INDONESIA_(M)_TELKOMSEL"|LAST|"SPECIAL_WORLD_GRP_7_FA_2_TELKOMSEL"
Can someone... (7 Replies)
Discussion started by: shis100
7 Replies
7. Shell Programming and Scripting
I need to replace dashes (i.e. -) if present from positions 351-357 with zero (i.e. 0), I also need to replace dash (i.e “-“) if present between position 024-043 with zero (i.e. 0) & I replace " " (i.e. 2 space characters) if present at position 381-382 with "04". Total length of record is 413.... (11 Replies)
Discussion started by: lancesunny
11 Replies
8. Shell Programming and Scripting
AWK Gurus,
data:
srvhcm01 AZSCI
srvhcm01 AZSDB
srvhcm01 BZSDB
srvhcm01 E2QDI31
srvhcm01 YPDCI
srvhcm01 YPDDB
srvhcm01 UV2FSCR
srvhcm01 UV2FSBI
srvhcm01 UV2FSXI
srvhcm01 UV2FSUC
srvhcm01 UV2FSEP
srvhcm01 UV2FSRE
srvhcm01 NASCI
srvhcm01 NASDB
srvhcm01 UV2FSSL
srvhcm01 UV2FSDI (7 Replies)
Discussion started by: rveri
7 Replies
9. UNIX for Beginners Questions & Answers
please use code tags, thanks
Initially olcDatabase={2}config.ldif file was in non-prod and it does not have any entries of database and password as well that is why I was getting error as “ldap_bind: Invalid credentials (49)”¯ , I was comparing with my production olcDatabase={2}config.ldif file ... (1 Reply)
Discussion started by: Bibhusisa
1 Replies
10. Shell Programming and Scripting
I am trying find files in sub dir with certain tags using tag command, and add the period to the beginning. I can't use chflags hidden {} cause it doesn't add period to the beginning of the string for web purpose. So far with my knowledge, I only know mdfind or tag can be used to search files with... (6 Replies)
Discussion started by: Nexeu
6 Replies
LEARN ABOUT MOJAVE
bindtags
bindtags(n) Tk Built-In Commands bindtags(n)
__________________________________________________________________________________________________________________________________________________
NAME
bindtags - Determine which bindings apply to a window, and order of evaluation
SYNOPSIS
bindtags window ?tagList?
_________________________________________________________________
DESCRIPTION
When a binding is created with the bind command, it is associated either with a particular window such as .a.b.c, a class name such as But-
ton, the keyword all, or any other string. All of these forms are called binding tags. Each window contains a list of binding tags that
determine how events are processed for the window. When an event occurs in a window, it is applied to each of the window's tags in order:
for each tag, the most specific binding that matches the given tag and event is executed. See the bind command for more information on the
matching process.
By default, each window has four binding tags consisting of the name of the window, the window's class name, the name of the window's near-
est toplevel ancestor, and all, in that order. Toplevel windows have only three tags by default, since the toplevel name is the same as
that of the window. The bindtags command allows the binding tags for a window to be read and modified.
If bindtags is invoked with only one argument, then the current set of binding tags for window is returned as a list. If the tagList argu-
ment is specified to bindtags, then it must be a proper list; the tags for window are changed to the elements of the list. The elements of
tagList may be arbitrary strings; however, any tag starting with a dot is treated as the name of a window; if no window by that name
exists at the time an event is processed, then the tag is ignored for that event. The order of the elements in tagList determines the
order in which binding scripts are executed in response to events. For example, the command
bindtags .b {all . Button .b}
reverses the order in which binding scripts will be evaluated for a button named .b so that all bindings are invoked first, following by
bindings for .b's toplevel ("."), followed by class bindings, followed by bindings for .b. If tagList is an empty list then the binding
tags for window are returned to the default state described above.
The bindtags command may be used to introduce arbitrary additional binding tags for a window, or to remove standard tags. For example, the
command
bindtags .b {.b TrickyButton . all}
replaces the Button tag for .b with TrickyButton. This means that the default widget bindings for buttons, which are associated with the
Button tag, will no longer apply to .b, but any bindings associated with TrickyButton (perhaps some new button behavior) will apply.
EXAMPLE
If you have a set of nested frame widgets and you want events sent to a button widget to also be delivered to all the widgets up to the
current toplevel (in contrast to Tk's default behavior, where events are not delivered to those intermediate windows) to make it easier to
have accelerators that are only active for part of a window, you could use a helper procedure like this to help set things up:
proc setupBindtagsForTreeDelivery {widget} {
set tags [list $widget [winfo class $widget]]
set w $widget
set t [winfo toplevel $w]
while {$w ne $t} {
set w [winfo parent $w]
lappend tags $w
}
lappend tags all
bindtags $widget $tags
}
SEE ALSO
bind(n)
KEYWORDS
binding, event, tag
Tk 4.0 bindtags(n)