ATR 72 Checklist
Normal Checklist
BATTERY START
BEFORE FIRST FLIGHT OF THE DAY
TURN AROUND
BEFORE ENGINE START
ENGINE START
PUSHBACK AND ENGINE START
TAXI
BEFORE TAKE OFF
AFTER TAKE OFF
DESCENT
APPROACH
FINAL
AFTER LANDING
PARKING CHECKLIST
SECURING
CheckList
Back
BATTERY START
PARKING BRAKE / PRESS
SET / CHECKED
BATTERY SWITCH
ON
MFC
TESTED / ON
CIRCUIT BREAKERS
CHECKED
GUST LOCK
ENGAGED
ENGINE LEVERS
SET GI / FSO
LANDING GEAR
DOWN / 3 GREEN
ENGINE FIRE 2
TESTED
PROP BRAKE
ON
FUEL PUMP 2
ON
COM 1
ON
ENGINE 2 START IN H-MODE
PERFORM
EMERG EXIT LIGHTS
ARMED
Save & Back
CheckList
Back
TURN AROUND
Securing Checks
reverse
DOCUMENTS
CHECKED / ON BOARD
EMERGENCY EQUIPMENT
CHECKED
GEAR PINS
STOWED
Flt Data / CVR
set / on
Engine Test
performed
Trims
checked / set
Parking Brake / Press
set / checked
Engine Levers
set GI / FSO
Gust Lock
engaged
Landing Elevation
set
Anti Skid
tested
Engine Control
set
Engine Fire 1+2
tested
Prop Brake
on
Cabin Signs
set
Circuit Breakers
checked
PREFLIGHT INSPECTION
COMPLETED
Save & Back
CheckList
Back
BEFORE ENGINE START
FUEL QUANTITY / FU
___ / ___
TORQUE BUGS
___% OBJ TORQUE
COM / NAV - EQUIPMENT
SET FOR DEP. ___
ALTIMETERS
___ hPa / ___ FT
NOSE WHEEL STEERING
ON / (OFF for pushback)
SPEED MARKS/ BUG/ TRIM
SET/___t/___COND/___°
Save & Back
CheckList
Back
ENGINE START
Fuel Pumps
on
Beacon / Wing Light
ON
PARKING BRAKE
SET / PRESS CHECKED
DOORS
CLOSED
White Lights
extinguished
Gen 2 / Ext Pwr PB
checked / off
Emerg Exit Lights
armed
ENGINE(S)
( 2 / BOTH) STARTED
FLAPS
SET / INDICATING 15
FLAPS
SET / INDICATING 15
GPU / CHOCKS
REMOVED
ENGINE TEST
PERFORMED
CABIN REPORT FOR TAXI
RECEIVED
TAIL PROP
ON BOARD
Save & Back
CheckList
Back
PUSHBACK AND ENGINE START
H – Mode
started
Gen 2 / Ext Pwr PB
checked / off
Emerg Exit Lights
armed
Beacon / Wing Light
ON
Fuel Pumps
ON
DOORS
CLOSED
GPU / CHOCKS
REMOVED
PARKING BRAKE
AS REQ BY GND CREW
NOSE WHEEL STEERING
OFF
TAIL PROP
ON BOARD
Save & Back
CheckList
Back
TAXI
Taxi Light
ON
BRAKES
CHECKED
ENGINES
STARTED
COND LEVERS
MAX RPM / AUTO
ANTI- / DEICE / WX RADAR
TESTED
T/O CONFIG
TESTED
ADU
SET
OVERBOARD VALVE
AUTO
CABIN REPORT FOR T/O
RECEIVED
Save & Back
CheckList
Back
BEFORE TAKE OFF
XPDR
Alt
CCAS
recall / T/O inhi
External Lights
ON
Engine Start Selector
cont relight (if avail.)


goeckeler.com
You just made it to the private homepage of the Göckeler family. This site is intended for our friends and relatives - who live in Germany, England, the U.S., and many other countries. If the idea to visit us may cross their mind, this is the place to look for directions and stuff.
Well, and as we are a family now, this is of course the place for all the cute baby pictures.
Of course everyone is invited to browse our site. Feel free. May-be one or the other is inclined to write us an email, and if it just to tell us how impressive this homepage is ;-)
New layout, new provider, more space, more pictures, complete revision of the sites. And all pages also in English. Hope you like the new layout.
Missing a digital camera means it takes a bit longer to present an album online. Thus we only started of with the first gymnastics session of our offspring.


WSO2 Web Services Framework/Ruby v 1.0.0 Features
Feature |
Description |
|---|---|
Comprehensive Support for Web Services Standards |
WSO2 WSF/Ruby supports the basic Web services standards including SOAP 1.1 and SOAP 1.2. WSO2 WSF/Ruby also supports the following WS-* specifications:
|
Proven Interoperability |
WSO2 WSF/Ruby features proven interoperability with Microsoft .NET, WSO2 WSAS (Apache Axis2/Java based Web services application server) and other J2EE implementations. The basic SOAP level interoperability as well as WS-* specification implementations have been tested and proven to interoperate. |
Portability and Platform Support |
WSO2 WSF/Ruby has been tested on:
|
| Attachments with Web Services and Clients | You can send and receive attachments with SOAP messages both in optimized as well as non optimized formats with MTOM support. |
| Secure Web Services and Clients | You can send messages with UsernameToken, and with TimeStamp
support. WSO2 WSF/Ruby extension also supports advanced WS-Security features including encryption and signing of SOAP messages. |
| Reliable Web Services and Clients | Reliable messaging is supported for both services and clients. Basic SOAP messages as well as messages with attachments can be sent in a reliable way. |
| REST Support | A single service can be exposed both as a SOAP style as well as a REST style service. The client API also supports invoking REST services using HTTP GET and POST methods. |
| Class mapping for services | This is one of the key features supported in the initial release of WSO2 WSF/Ruby. With this the user can provide a class and expose the class operations as service operations. |


Preparation time
overnight
Cooking time
over 2 hours
Serves
Serves 4
Belly pork recipes tend to benefit from a slow cook. Sat Baines uses a water bath for his creation.
Equipment and preparation: You’ll need a temperature-controlled water bath and sous vide bags.
Rub the meat side of the pork belly with the salt. Cover with clingfilm and chill in the fridge for 24 hours.
Remove the pork from the fridge and rinse under cold running water for at least 20 minutes.
Place the pork in a sous vide bag and vacuum seal.
Heat a water bath to 72C/160F and place the pork in the bath for 24 hours. Alternatively, place into a pressure cooker, cover and cook for one hour.
Once cooked, place the sealed pork between two baking trays. Gently press down with a weight and chill in the fridge for a minimum of 12 hours. Once pressed cut the pork into squares.
Place the soy, honey, mirin and sesame oil into a bowl and whisk together until fully emulsified into a teriyaki sauce.
Heat a frying pan until hot. Add the pork skin-side down and fry on each side until caramelised. Spoon the teriyaki sauce over to glaze the pork. Remove the meat from the pan and place onto a chopping board. Place the shonka ham over the top and fold over the edges.
For the piccalilli, place the cauliflower and onion into a colander. Cover with the salt and set aside for 24 hours. Rinse away the salt thoroughly under cold running water.
Mix the cauliflower and onion with the cucumber until well combined.
Bring the vinegars to the boil with the chilli, turn off the heat and set aside to infuse for 20 minutes.
Bring the vinegar mixture to the boil again. Stir in the corn flour, turmeric, mustard and sugar and simmer for three minutes.
Pour the simmering liquid over the vegetables, transfer to a food processor and blend until smooth. Pass through a fine sieve and chill in the fridge until required.
Meanwhile, cut the apples into 1.5cm/½in cubes. Dress the cubes with the lemon juice, salt and a drop of apple balsamic.
For the cauliflower salad, mix the cauliflower with lemon juice and sea salt.
To serve, brush the piccalilli across the plate. Add a piece of pork on top and scatter over the apple and finish with the cauliflower salad.


Capture Photo
Capture Editable Photo
From Photo Library
From Photo Album
Angular
Knockout
Show Alert


--- layout: post title: Assignment 2 in "Functional Programming Principles in Scala" from Coursera date: 2015-01-12 09:10:51.000000000 +08:00 categories: - scala tags: - coursera - scala status: publish type: post published: true meta: _wpas_skip_facebook: '1' _wpas_skip_google_plus: '1' _wpas_skip_twitter: '1' _wpas_skip_linkedin: '1' _wpas_skip_tumblr: '1' _wpas_skip_path: '1' _publicize_pending: '1' _rest_api_published: '1' _rest_api_client_id: '-1' author: login: balloontin email<EMAIL_ADDRESS>display_name: balloontin first_name: '' last_name: '' ---
We will work with sets of integers.
As an example to motivate our representation, how would you represent the set of all negative integers? You cannot list them all… one way would be so say: if you give me an integer, I can tell you whether it’s in the set or not: for 3
, I say ‘no’; for -1
, I say yes
.
Mathematically, we call the function which takes an integer as argument and which returns a boolean indicating whether the given integer belongs to a set, the characteristic function of the set. For example, we can characterize the set of negative integers by the characteristic function (x: Int) => x < 0
.
Therefore, we choose to represent a set by its characterisitc function and define a type alias for this representation:
type Set = Int => Boolean
Using this representation, we define a function that tests for the presence of a value in a set:
def contains(s: Set, elem: Int): Boolean = s(elem)
Let’s start by implementing basic functions on sets.
def singletonSet(elem: Int): Set
Now that we have a way to create singleton sets, we want to define a function that allow us to build bigger sets from smaller ones.
union
, intersect
, and diff
, which takes two sets, and return, respectively, their union, intersection and differences. diff(s, t)
returns a set which contains all the elements of the set s
that are not in the set t
. These functions have the following signatures:
def union(s: Set, t: Set): Set
def intersect(s: Set, t: Set): Set
def diff(s: Set, t: Set): Set
filter
which selects only the elements of a set that are accepted by a given predicate p
. The filtered elements are returned as a new set. The signature of filter
is as follows:
def filter(s: Set, p: Int => Boolean): Set
In this part, we are interested in functions used to make requests on elements of a set. The first function tests whether a given predicate is true for all elements of the set. This forall
function has the following signature:
def forall(s: Set, p: Int => Boolean): Boolean
Note that there is no direct way to find which elements are in a set. contains
only allows to know whether a given element is included. Thus, if we wish to do something to all elements of a set, then we have to iterate over all integers, testing each time whether it is included in the set, and if so, to do something with it. Here, we consider that an integer x
has the property -1000 <= x <= 1000
in order to limit the search space.
forall
using linear recursion. For this, use a helper function nested in forall
. Its structure is as follows (replace the ???
):
def forall(s: Set, p: Int => Boolean): Boolean = {
def iter(a: Int): Boolean = {
if (???) ???
else if (???) ???
else iter(???)
}
iter(???)
}
forall
, implement a function exists
which tests whether a set contains at least one element for which the given predicate is true. Note that the functions forall
and exists
behave like the universal and existential quantifiers of first-order logic.
def exists(s: Set, p: Int => Boolean): Boolean
map
which transforms a given set into another one by applying to each of its elements the given function. map
has the following signature:
def map(s: Set, f: Int => Int): Set
object FunSets {
type Set = Int => Boolean
def contains(s: Set, elem: Int): Boolean = s(elem)
def singletonSet(elem: Int): Set={
(x : Int) => x==elem
}
def union(s: Set, t: Set): Set = {
(x:Int ) => s(x)||t(x)
}
def intersect(s: Set, t: Set): Set = {
(x:Int) => s(x)&&t(x)
}
def diff(s: Set, t: Set): Set = {
(x:Int) => s(x)&& !t(x)
}
def filter(s: Set, p: Int => Boolean): Set ={
(x:Int) => s(x)&& p(x)
}
/**
* The bounds for `forall` and `exists` are +/- 1000.
*/
val bound = 1000
def forall(s: Set, p: Int => Boolean): Boolean = {
def iter(a: Int): Boolean = {
if (a < -bound) true
else if (contains(s,a) && !p(a)) false
else iter(a-1)
}
iter(bound)
}
def exists(s: Set, p: Int => Boolean): Boolean = {
!(forall ( s, (x:Int)=> !p(x)))
}
def map(s: Set, f: Int => Int): Set = {
(x:Int) => exists(s, (a:Int)=> f(a) == x)
}
def toString(s: Set): String = {
val xs = for (i <- -bound to bound if contains(s, i)) yield i
xs.mkString("{", ",", "}")
}
def printSet(s: Set) {
println(toString(s))
}
}


Connection Lost
Connection to MQTT broker lost :-(
Tinters That Exist:
Tinter
Manufacturer
Model
S/N
Status
???
C
M
Y
Dispense


Archaeological periods – the challenge
Archaeological chronology is a complex and sometimes messy system of archaeological periods that enables archaeologists to determine the phase of a culture within a time sequence. The main definition of an archaeological period is not based on an absolute time-span but rather on distinctive characteristics of past human activities. For example, the Neolithic period is characterized by the occurrence of pottery and farming. Because the knowledge (and people) was spreading slowly, it often occurred that one region just started to learn about it, while another region was already characterized by what we call the Bronze Age. An archaeological period can, therefore, be present at different times in different places. However, not all regions followed the same period sequence. For example, while in some regions a direct transition from Neolithic to the Bronze Age has been confirmed, in other regions Neolithic was first followed by Chalcolithic.
In addition to the general periods, archaeologists also use more detailed periods or phases to describe particulars of one material culture. Because each material culture is bound to a specific region during a specific time-span, the same goes for such archaeological periods. They are often named after prominent archaeological sites where the distinctive artefacts were found (e.g. Argissa I in Thessaly, Greece). Such archaeological periods/phases may overlap in time, but they are region specific. Furthermore, because several researchers worked on the same material culture, many developed their own chronological system. The result is many archaeological periods/phases describing the same material culture within the same region, but with a bit different sequencing of sub-phases.
Taking all this into account it becomes obvious that structuring and formalizing archaeological chronology is a challenging task. The chronology of the DEFC app is an attempt to provide an overview of archaeological periods used in Greece and Anatolia for the period of as early as 10000 (Anatolia) to ca. 2000 BC. To contribute to linked data and to ensure the possibility for their reuse, the periods of the app were linked to PeriodO – the public domain gazetteer of scholarly definitions of historical, art-historical, and archaeological periods.
Creating the DEFC chronology
DEFC chronology was created in collaboration with Anatolian Aegean Prehistoric Phenomena (AAPP) research group (OREA ÖAW) using existing literature and relying on the experience and knowledge of the research group members. The periods were gathered separately for the following regions covering periods from the Neolithic to Early Bronze Age:
| Region | Archaeological period coverage |
|---|---|
| Anatolia |
Central, Western, Southwestern Anatolia General Anatolia, East Aegean |
| Central and Southern Greece | Peloponnese, Central Greece, Epirus-Northwestern Greece, Ionian Islands, Western Greece, Cyclades |
| Thessaly | Thessaly |
| Macedonia/Thrace | Macedonia, Thrace |
| Macedonia |
Eastern Macedonia Central Macedonia Western Macedonia |
| Crete | *3 different chronology systems for Crete by different authors |
To create the DEFC chronology the following bibliographic resources have been used (the absolute dates were copied directly or derived from the contents).
- Aurenche, O., Cauvin, J., Cauvin, M. C., Copeland, I., Hours, F., Sanlaville, P., Chronologie et organisation de l’espace dans le Proche-Orient de 12 000 à 5 600 avant J.-C. In: Cauvin J. et Sanlaville P. (éd.), Préhistoire du Levant, (Paris 1981), 571–601.
- Alram-Stern, E. Die ägäische Frühzeit. Die Frühbronzezeit in Griechenland mit Ausnahme von Kreta (2004, Wien).
- Alram-Stern, E., A. Dousougli-Zachos, Die deutschen Ausgrabungen 1941 auf der Visviki-Magula/Velestino. Die neolithischen Befunde und Funde. Mit Beiträgen von Maximilian Bergner, † Franz Bertsch, Caroline Dürauer, Alfred Galik, Helmut Kroll, Areti Pentedeka, Ernst Pernicka, Gunter Schöbel, Kostas Zachos. Beiträge zur ur- und frühgeschichtlichen Archäologie des Mittelmeer-Kulturraumes 36, (Bonn 2015), 92.
- Clare, L., Weninger, B., The Dispersal of Neolithic Lifeways: Absolute Chronology and Rapid Climate Change, in: M. Özdoğan, N. Başgelen, P. Kuniholm (Eds.), Neolithic in Turkey, Vol 6: 10500-5200 BC: Environment settlement, flora, fauna, dating, symbols of belief, with views from north, south, east, and west (Istanbul 2014), 1–65.
- Efe, T., Demircihüyük III.2. Die Keramik 2. C. Die Frühbronzezeitliche Keramik der jüngeren Phasen (ab Phase H) (Mainz 1988), 117, Fig. 98.
- Evans, J. D., Excavations in the Neolithic Settlement at Knossos, 1957-60, BSA 59, 1964, 132–240.
- Momigliano, M. Late Prepalatial (EM III-MM IA): South Front House Foundation Trench, Upper East Well, and House C / RRS Fill groups, in: N. Momigliano. Knossos Pottery Handbook: Neolithic and Bronze Age (Minoan), (London 2007), 79-103.
- Özdoğan, M., Başgelen, N., Kuniholm, P. (Eds.), Neolithic in Turkey, Vol 6: The Euphrates Basin, (Istanbul 2011), 281.
- Reingruber, A., Die Argissa-Magula II. Das frühe und beginnende mittlere Neolithikum im Lichte transägäischer Beziehungen, Beiträge zur Ur- und Frühgeschichtlichen Archäologie des Mittelmeer-Kulturraumes 35 (Bonn 2008).
- Schoop, U. D., Das anatolische Chalkolithikum. Eine chronologische Untersuchung zur vorbronzezeitlichen Kultursequenz im nördlichen Zentralanatolien und den angrenzenden Gebieten, Urgeschichtliche Studien 1 (Großschönau 2005).
- Tomkins, P., Neolithic: Strata IX–VII, VII–VIB, VIA–V, IV, IIIB, IIIA, IIB, IIA and IC Groups, British School at Athens Studies, Vol. 14, Knossos Pottery Handbook: Neolithic and Bronze Age (Minoan) (2007), pp. 9-48, 1-2.
- Tsirtsoni, Z., Concluding remarks, in: Z. Tsirtsoni (ed.), The Human Face of Radiocarbon. Reassessing chronology in prehistoric Greece and Bulgaria, 5000-3000 cal BC., 453-464.
- Vagnetti, L., Belli, P., Characters and Problems of the Final Neolithic in Crete, Studi Micenei ed Egeo-anatolici 19, 1978, 125-163.
- Wilson, D., Early Prepalatial (EM I-EM II): EM I Well, West Court House, North-East Magazines and South Front Groups, in: N. Momigliano. Knossos Pottery Handbook: Neolithic and Bronze Age (Minoan), (London 2007), 49-77.
Linking to PeriodO
PeriodO is an online gazetteer for historical, art-historical, and archaeological periods. Using PeriodO it is possible to define an archaeological period through an absolute time-span and the region of interest. As the final result, a permalink for each defined period is created, which can be used as a URI to link two or more online sources. All periods from the DEFC chronology were defined using PeriodO and then linked with the periods listed in the DEFC app.
The periods from the DEFC chronology were grouped into three PeriodO collections. The so-called DEFC Project collection contains archaeological periods (i.e. the absolute time-span) that were derived but not literally copied from the cited literature. The other three collections (Schoop – Greiner 2005, Clare – Weiniger 2014, Tomkins 2007) include periods exactly as they were defined by the authors of cited works and as such also used in the DEFC chronology.
Collection permalinks:
The collections can be reused by other projects investigating Neolithic, Chalcolithic, and Early Bronze Age in Greece and Anatolia.
Back to Main blog page


WELCOME
TO DELANI STUDIO
AMAZING PEOPLE ARE MAKING DESIGNS IN A FUN ENVIRONMENT
When you work with us,you are apart of a team of committed collaboratorts.All aspects of our softwear development process are intergrated,interactive and agile
Our approach unifies design ,development and product management to create exceptional products
We start each project by understanding your business goals, the user's needs and the product requirements
Then we help translate them into effective and elegant solutions
Before we sign a contact or write a line of code our team will speand the necessary time needed to understand your product vision
The outcome of this scoping session is a proposal or high-level statement of work.
based on your requirements,we can provide accomplete offerings or just pieces you need
Our design practice offers a full range of services including a brand strategy,interaction and visual design and user experience testing.
Throught your project, our designers create and implement visual design and workflows solict users feedback and work with you to make sure what gets build is what is neede .
All engineers are fluent in the latest enterprise, mobile and web development technologies
They collaborate with your team to write and improve your code on a daily basis,using proven practices such as test-driven development and pair programming
Planning development is iterative.Because we are constantly coding and texting, the products we build are always ready to go live
This iterative process allows for change as business requirements evolve
Project 1
Project 1
Project 1
Project 1
Project 1
Project 1
Project 1
Project 1


Stock Symbol is required.
Stock Market is required.
Stock Name is required.
Stock Last Rate is required.
Stock ChangeFromPreviousClose is required.
Stock PreviousClose is required.


Lucid to the Moon
2021 Product Summit
A two-day summit of talks, activities, and workshops for Lucid's Product org.
Day 1
Wednesday, June 9th
Join Now
View Agenda
Day 2
Thursday, June 10th
Join Now
View Agenda
The goal of this event is to build team unity, become better at our craft, align on our vision and strategy, and motivate us into the coming year.
A Look Back at Product Summit 2020
Previous
Next


the and with for (). The & al., etÂ binding â€". Mpro that (), docking {background ACE was are hydrogen interaction through main margin natural SARS-CoV- were {border-style âˆ’. bioavailability has its px;} #ffffff;} MM-GBSA from potential site âˆ’.â€‰Kcal/mol also found have Journal coronavirus drug human hydroxyl catalytic protease residues ADME against receptor reported ring score their viral which acid clinical energies host A., COVID- Figure group inhibitor leads molecules two Avicularin HIE affinity moiety molecular protein this (Figure ,-Di-O-galloylshikimic SARS-CoV Scutellarein active al. all between bond groups oral screened these using âˆ’./ -glucoside ./s--- Delphinidin antiviral both chain interact inÂ multiple other px; shows side spike {font-family ACE, GS- M., SARS activity analysis bind energy font-size four inside low poses protein, proteins showed target top Ï€-Ï€ âˆ’./âˆ’. (Mpro) Molecular ORF been bonds cells compound compounds computational double; due form interactions involved novel nucleus pose present residue scores screening stacking structure studies subunit. sugar vitro (iii) ,-diglucoside -glucoside, ACE. ARG Chemical Docking Food Polygonum S., Structure This While approach avicularin border-color border-width calculations can crystal domain drugs effective free further hydroxyls inhibitory into key lead membrane metabolites only pharmacokinetic phenyl presence region respiratory responsible secondary solid; solubility study subsite via {font-style {font-weight âˆ’.â€‰Kcal/mol. (i), (ii) ASP Biomolecular Chemistry, Docked FDA GLN GLU However, Hydroxychloroquine MM-GB/SA Mpro. Natural P., RNA Remdesivir Science T., THR acute addition amine amino anthocyanin anthocyanins associated benzene benzoyl bioavailability. bold bonded bonding but cancer candidates cell cleft collab: courier; em; encodes entry forms good having high highest hydrophobic inhibit less oxygen plant polar products properties pt;} replication respectively. selected several severe silico similar software study. treatment under used virus water zinc â€¦


Brian Price
As a military veteran of 25 years of service, I have a vast amount of experience and skills that will be beneficial to an employer. Although not employed by the military in the field of Web Design, I decided upon my release of military service to expand my horizons into this field. As a graduate of Columbia Southern University and, more recently, Southwestern Illinois College, I am excited to put my education and experience to use.
Please visit my other ePortfolio pages to learn more about my web design skills and review my resume for more information on my other skill-sets. If you are interested in reaching out to me, I'd love to connect.
Thank you for taking the time to visit my website. Have a great day!


- The default location in which `dirs -S' and `dirs -L' look for a history file. If unset, ~/.cshdirs is used. Because only ~/.tcshrc is normally sourced before ~/.cshdirs, dirsfile should be set in ~/.tcshrc rather than ~/.login.
- dirstack (+)
- An array of all the directories on the directory stack. `$dirstack[1]' is the current working directory, `$dirstack[2]' the first directory on the stack, etc. Note that the current working directory is `$dirstack[1]' but `=0' in directory stack substitutions, etc. One can change the stack arbitrarily by setting dirstack, but the first element (the current working directory) is always correct. See also the cwd and owd shell variables.
- dspmbyte (+)
-
Has an affect iff 'dspm' is listed as part of the version shell variable.
If set to `euc', it enables display and editing EUC-kanji(Japanese) code.
If set to `sjis', it enables display and editing Shift-JIS(Japanese) code.
If set to `big5', it enables display and editing Big5(Chinese) code.
If set to `utf8', it enables display and editing Utf8(Unicode) code.
If set to the following format, it enables display and editing of original
multi-byte code format:
-
- > set dspmbyte = 0000....(256 bytes)....0000
The table requires just 256 bytes. Each character of 256 characters corresponds (from left to right) to the ASCII codes 0x00, 0x01, ... 0xff. Each character is set to number 0,1,2 and 3. Each number has the following meaning:
0 ... not used for multi-byte characters.
1 ... used for the first byte of a multi-byte character.
2 ... used for the second byte of a multi-byte character.
3 ... used for both the first byte and second byte of a multi-byte character.
Example:
If set to `001322', the first character (means 0x00 of the ASCII code) and second character (means 0x01 of ASCII code) are set to `0'. Then, it is not used for multi-byte characters. The 3rd character (0x02) is set to '1', indicating that it is used for the first byte of a multi-byte character. The 4th character(0x03) is set '3'. It is used for both the first byte and the second byte of a multi-byte character. The 5th and 6th characters (0x04,0x05) are set to '2', indicating that they are used for the second byte of a multi-byte character.The GNU fileutils version of ls cannot display multi-byte filenames without the -N ( --literal ) option. If you are using this version, set the second word of dspmbyte to "ls". If not, for example, "ls-F -l" cannot display multi-byte filenames.
Note:
This variable can only be used if KANJI and DSPMBYTE has been defined at compile time.
-
- dunique (+)
- If set, pushd removes any instances of name from the stack before pushing it onto the stack.
- echo
- If set, each command with its arguments is echoed just before it is executed. For non-builtin commands all expansions occur before echoing. Builtin commands are echoed before command and filename substitution, because these substitutions are then done selectively. Set by the -x command line option.
- echo_style (+)
- The style of the echo builtin. May be set to
-
- bsd
- Don't echo a newline if the first argument is `-n'.
- sysv
- Recognize backslashed escape sequences in echo strings.
- both
- Recognize both the `-n' flag and backslashed escape sequences; the default.
- none
- Recognize neither.
Set by default to the local system default. The BSD and System V options are described in the echo(1) man pages on the appropriate systems.
- edit (+)
- If set, the command-line editor is used. Set by default in interactive shells.
- ellipsis (+)
- If set, the `%c'/`%.' and `%C' prompt sequences (see the prompt shell variable) indicate skipped directories with an ellipsis (`...') instead of `/<skipped>'.
- fignore (+)
- Lists file name suffixes to be ignored by completion.
- filec
- In tcsh, completion is always used and this variable is ignored by default. If edit is unset, then the traditional csh completion is used. If set in csh, filename completion is used.
- gid (+)
- The user's real group ID.
- group (+)
- The user's group name.
- highlight
-
If set, the incremental search match (in i-search-back and
i-search-fwd) and the region between the mark and the cursor are
highlighted in reverse video.
Highlighting requires more frequent terminal writes, which introduces extra overhead. If you care about terminal performance, you may want to leave this unset.
- histchars
- A string value determining the characters used in History substitution (q.v.). The first character of its value is used as the history substitution character, replacing the default character `!'. The second character of its value replaces the character `^' in quick substitutions.
- histdup (+)
- Controls handling of duplicate entries in the history list. If set to `all' only unique history events are entered in the history list. If set to `prev' and the last history event is the same as the current command, then the current command is not entered in the history. If set to `erase' and the same event is found in the history list, that old event gets erased and the current one gets inserted. Note that the `prev' and `all' options renumber history events so there are no gaps.
- histfile (+)
- The default location in which `history -S' and `history -L' look for a history file. If unset, ~/.history is used. histfile is useful when sharing the same home directory between different machines, or when saving separate histories on different terminals. Because only ~/.tcshrc is normally sourced before ~/.history, histfile should be set in ~/.tcshrc rather than ~/.login.
- histlit (+)
- If set, builtin and editor commands and the savehist mechanism use the literal (unexpanded) form of lines in the history list. See also the toggle-literal-history editor command.
- history
- The first word indicates the number of history events to save. The optional second word (+) indicates the format in which history is printed; if not given, `%h\t%T\t%R\n' is used. The format sequences are described below under prompt; note the variable meaning of `%R'. Set to `100' by default.
- home
- Initialized to the home directory of the invoker. The filename expansion of `~' refers to this variable.
- ignoreeof
- If set to the empty string or `0' and the input device is a terminal, the end-of-file command (usually generated by the user by typing `^D' on an empty line) causes the shell to print `Use "exit" to leave tcsh.' instead of exiting. This prevents the shell from accidentally being killed. Historically this setting exited after 26 successive EOF's to avoid infinite loops. If set to a number n, the shell ignores n - 1 consecutive end-of-files and exits on the nth. (+) If unset, `1' is used, i.e., the shell exits on a single `^D'.
- implicitcd (+)
- If set, the shell treats a directory name typed as a command as though it were a request to change to that directory. If set to verbose, the change of directory is echoed to the standard output. This behavior is inhibited in non-interactive shell scripts, or for command strings with more than one word. Changing directory takes precedence over executing a like-named command, but it is done after alias substitutions. Tilde and variable expansions work as expected.
- inputmode (+)
- If set to `insert' or `overwrite', puts the editor into that input mode at the beginning of each line.
- killdup (+)
- Controls handling of duplicate entries in the kill ring. If set to `all' only unique strings are entered in the kill ring. If set to `prev' and the last killed string is the same as the current killed string, then the current string is not entered in the ring. If set to `erase' and the same string is found in the kill ring, the old string is erased and the current one is inserted.
- killring (+)
- Indicates the number of killed strings to keep in memory. Set to `30' by default. If unset or set to less than `2', the shell will only keep the most recently killed string. Strings are put in the killring by the editor commands that delete (kill) strings of text, e.g. backward-delete-word, kill-line, etc, as well as the copy-region-as-kill command. The yank editor command will yank the most recently killed string into the command-line, while yank-pop (see Editor commands) can be used to yank earlier killed strings.
- listflags (+)
- If set to `x', `a' or `A', or any combination thereof (e.g., `xA'), they are used as flags to ls-F, making it act like `ls -xF', `ls -Fa', `ls -FA' or a combination (e.g., `ls -FxA'): `a' shows all files (even if they start with a `.'), `A' shows all files but `.' and `..', and `x' sorts across instead of down. If the second word of listflags is set, it is used as the path to `ls(1)'.
- listjobs (+)
- If set, all jobs are listed when a job is suspended. If set to `long', the listing is in long format.
- listlinks (+)
- If set, the ls-F builtin command shows the type of file to which each symbolic link points.
- listmax (+)
- The maximum number of items which the list-choices editor command will list without asking first.
- listmaxrows (+)
- The maximum number of rows of items which the list-choices editor command will list without asking first.
- loginsh (+)
- Set by the shell if it is a login shell. Setting or unsetting it within a shell has no effect. See also shlvl.
- logout (+)
- Set by the shell to `normal' before a normal logout, `automatic' before an automatic logout, and `hangup' if the shell was killed by a hangup signal (see Signal handling). See also the autologout shell variable.
- The names of the files or directories to check for incoming mail, separated by whitespace, and optionally preceded by a numeric word. Before each prompt, if 10 minutes have passed since the last check, the shell checks each file and says `You have new mail.' (or, if mail contains multiple files, `You have new mail in name.') if the filesize is greater than zero in size and has a modification time greater than its access time.
-
If you are in a login shell, then no mail file is reported unless it has been modified after the time the shell has started up, to prevent redundant notifications. Most login programs will tell you whether or not you have mail when you log in.
If a file specified in mail is a directory, the shell will count each file within that directory as a separate message, and will report `You have n mails.' or `You have n mails in name.' as appropriate. This functionality is provided primarily for those systems which store mail in this manner, such as the Andrew Mail System.
If the first word of mail is numeric it is taken as a different mail checking interval, in seconds.
Under very rare circumstances, the shell may report `You have mail.' instead of `You have new mail.'
- matchbeep (+)
- If set to `never', completion never beeps. If set to `nomatch', it beeps only when there is no match. If set to `ambiguous', it beeps when there are multiple matches. If set to `notunique', it beeps when there is one exact and other longer matches. If unset, `ambiguous' is used.
- nobeep (+)
- If set, beeping is completely disabled. See also visiblebell.
- noclobber
- If set, restrictions are placed on output redirection to insure that files are not accidentally destroyed and that `>>' redirections refer to existing files, as described in the Input/output section.
- noding
- If set, disable the printing of `DING!' in the prompt time specifiers at the change of hour.
- noglob
- If set, Filename substitution and Directory stack substitution (q.v.) are inhibited. This is most useful in shell scripts which do not deal with filenames, or after a list of filenames has been obtained and further expansions are not desirable.
- nokanji (+)
- If set and the shell supports Kanji (see the version shell variable), it is disabled so that the meta key can be used.
- nonomatch
- If set, a Filename substitution or Directory stack substitution (q.v.) which does not match any existing files is left untouched rather than causing an error. It is still an error for the substitution to be malformed, e.g., `echo [' still gives an error.
- nostat (+)
- A list of directories (or glob-patterns which match directories; see Filename substitution) that should not be stat(2)ed during a completion operation. This is usually used to exclude directories which take too much time to stat(2), for example /afs.
- notify
- If set, the shell announces job completions asynchronously. The default is to present job completions just before printing a prompt.
- oid (+)
- The user's real organization ID. (Domain/OS only)
- owd (+)
- The old working directory, equivalent to the `-' used by cd and pushd. See also the cwd and dirstack shell variables.
- padhour
- If set, enable the printing of padding '0' for hours, in 24 and 12 hour formats. E.G.: 07:45:42 vs. 7:45:42
- path
- A list of directories in which to look for executable commands. A null word specifies the current directory. If there is no path variable then only full path names will execute. path is set by the shell at startup from the PATH environment variable or, if PATH does not exist, to a system-dependent default something like `(/usr/local/bin /usr/bsd /bin /usr/bin .)'. The shell may put `.' first or last in path or omit it entirely depending on how it was compiled; see the version shell variable. A shell which is given neither the -c nor the -t option hashes the contents of the directories in path after reading ~/.tcshrc and each time path is reset. If one adds a new command to a directory in path while the shell is active, one may need to do a rehash for the shell to find it.
- printexitvalue (+)
- If set and an interactive program exits with a non-zero status, the shell prints `Exit status'.
- prompt
- The string which is printed before reading each command from the terminal. prompt may include any of the following formatting sequences (+), which are replaced by the given information:
-
- %/
- The current working directory.
- %~
- The current working directory, but with one's home directory represented by `~' and other users' home directories represented by `~user' as per Filename substitution. `~user' substitution happens only if the shell has already used `~user' in a pathname in the current session.
- %c[[0]n], %.[[0]n]
- The trailing component of the current working directory, or n trailing components if a digit n is given. If n begins with `0', the number of skipped components precede the trailing component(s) in the format `/<skipped>trailing'. If the ellipsis shell variable is set, skipped components are represented by an ellipsis so the whole becomes `...trailing'. `~' substitution is done as in `%~' above, but the `~' component is ignored when counting trailing components.
- %C
- Like %c, but without `~' substitution.
- %h, %!, !
- The current history event number.
- %M
- The full hostname.
- %m
- The hostname up to the first `.'.
- %S (%s)
- Start (stop) standout mode.
- %B (%b)
- Start (stop) boldfacing mode.
- %U (%u)
- Start (stop) underline mode.
- %t, %@
- The time of day in 12-hour AM/PM format.
- %T
- Like `%t', but in 24-hour format (but see the ampm shell variable).
- %p
- The `precise' time of day in 12-hour AM/PM format, with seconds.
- %P
- Like `%p', but in 24-hour format (but see the ampm shell variable).
- \c
- c is parsed as in bindkey.
- ^c
- c is parsed as in bindkey.
- %%
- A single `%'.
- %n
- The user name.
- %j
- The number of jobs.
- %d
- The weekday in `Day' format.
- %D
- The day in `dd' format.
- %w
- The month in `Mon' format.
- %W
- The month in `mm' format.
- %y
- The year in `yy' format.
- %Y
- The year in `yyyy' format.
- %l
- The shell's tty.
- %L
- Clears from the end of the prompt to end of the display or the end of the line.
- %$
- Expands the shell or environment variable name immediately after the `$'.
- %#
- `>' (or the first character of the promptchars shell variable) for normal users, `#' (or the second character of promptchars) for the superuser.
- %{string%}
- Includes string as a literal escape sequence. It should be used only to change terminal attributes and should not move the cursor location. This cannot be the last sequence in prompt.
- %?
- The return code of the command executed just before the prompt.
- %R
- In prompt2, the status of the parser. In prompt3, the corrected string. In history, the history string.
`%B', `%S', `%U' and `%{string%}' are available in only eight-bit-clean shells; see the version shell variable.
The bold, standout and underline sequences are often used to distinguish a superuser shell. For example,
-
> set prompt = "%m [%h] %B[%@]%b [%/] you rang? "
tut [37] [2:54pm] [/usr/accts/sys] you rang? _
If `%t', `%@', `%T', `%p', or `%P' is used, and noding is not set, then print `DING!' on the change of hour (i.e, `:00' minutes) instead of the actual time.
Set by default to `%# ' in interactive shells.
- prompt2 (+)
- The string with which to prompt in while and foreach loops and after lines ending in `\'. The same format sequences may be used as in prompt (q.v.); note the variable meaning of `%R'. Set by default to `%R? ' in interactive shells.
- prompt3 (+)
- The string with which to prompt when confirming automatic spelling correction. The same format sequences may be used as in prompt (q.v.); note the variable meaning of `%R'. Set by default to `CORRECT>%R (y|n|e|a)? ' in interactive shells.
- promptchars (+)
- If set (to a two-character string), the `%#' formatting sequence in the prompt shell variable is replaced with the first character for normal users and the second character for the superuser.
- pushdtohome (+)
- If set, pushd without arguments does `pushd ~', like cd.
- pushdsilent (+)
- If set, pushd and popd do not print the directory stack.
- recexact (+)
- If set, completion completes on an exact match even if a longer match is possible.
- recognize_only_executables (+)
- If set, command listing displays only files in the path that are executable. Slow.
- rmstar (+)
- If set, the user is prompted before `rm *' is executed.
- rprompt (+)
- The string to print on the right-hand side of the screen (after the command input) when the prompt is being displayed on the left. It recognizes the same formatting characters as prompt. It will automatically disappear and reappear as necessary, to ensure that command input isn't obscured, and will appear only if the prompt, command input, and itself will fit together on the first line. If edit isn't set, then rprompt will be printed after the prompt and before the command input.
- savedirs (+)
- If set, the shell does `dirs -S' before exiting. If the first word is set to a number, at most that many directory stack entries are saved.
- savehist
- If set, the shell does `history -S' before exiting. If the first word is set to a number, at most that many lines are saved. (The number must be less than or equal to history.) If the second word is set to `merge', the history list is merged with the existing history file instead of replacing it (if there is one) and sorted by time stamp and the most recent events are retained. (+)
- sched (+)
- The format in which the sched builtin command prints scheduled events; if not given, `%h\t%T\t%R\n' is used. The format sequences are described above under prompt; note the variable meaning of `%R'.
- shell
- The file in which the shell resides. This is used in forking shells to interpret files which have execute bits set, but which are not executable by the system. (See the description of Builtin and non-builtin command execution.) Initialized to the (system-dependent) home of the shell.
- shlvl (+)
- The number of nested shells. Reset to 1 in login shells. See also loginsh.
- status
- The status of any error in a pipeline or a backquote expansion that is propagated as a result `status', unless `tcsh_posix_status' variable is set, and only the last command status is taken in account (the latter is default behaviour in POSIX-like shells). If it terminated abnormally, then 0200 is added to the status. Builtin commands which fail return exit status `1', all other builtin commands return status `0'.
- symlinks (+)
-
Can be set to several different values to control symbolic link (`symlink')
resolution:
-
If set to `chase', whenever the current directory changes to a directory containing a symbolic link, it is expanded to the real name of the directory to which the link points. This does not work for the user's home directory; this is a bug.
If set to `ignore', the shell tries to construct a current directory relative to the current directory before the link was crossed. This means that cding through a symbolic link and then `cd ..'ing returns one to the original directory. This affects only builtin commands and filename completion.
If set to `expand', the shell tries to fix symbolic links by actually expanding arguments which look like path names. This affects any command, not just builtins. Unfortunately, this does not work for hard-to-recognize filenames, such as those embedded in command options. Expansion may be prevented by quoting. While this setting is usually the most convenient, it is sometimes misleading and sometimes confusing when it fails to recognize an argument which should be expanded. A compromise is to use `ignore' and use the editor command normalize-path (bound by default to ^X-n) when necessary.
Some examples are in order. First, let's set up some play directories:
-
> cd /tmp
> mkdir from from/src to
> ln -s from/src to/dst
Here's the behavior with symlinks unset,
-
> cd /tmp/to/dst; echo $cwd
/tmp/to/dst
> cd ..; echo $cwd
/tmp/from
here's the behavior with symlinks set to `chase',
-
> cd /tmp/to/dst; echo $cwd
/tmp/from/src
> cd ..; echo $cwd
/tmp/from
here's the behavior with symlinks set to `ignore',
-
> cd /tmp/to/dst; echo $cwd
/tmp/to/dst
> cd ..; echo $cwd
/tmp/to
and here's the behavior with symlinks set to `expand'.
-
> cd /tmp/to/dst; echo $cwd
/tmp/to/dst
> cd ..; echo $cwd
/tmp/to
> cd /tmp/to/dst; echo $cwd
/tmp/to/dst
> cd ".."; echo $cwd
/tmp/from
> /bin/echo ..
/tmp/to
> /bin/echo ".."
..
Note that `expand' expansion 1) works just like `ignore' for builtins like cd, 2) is prevented by quoting, and 3) happens before filenames are passed to non-builtin commands.
-
> cd /tmp
-
- tcsh (+)
- The version number of the shell in the format `R.VV.PP', where `R' is the major release number, `VV' the current version and `PP' the patchlevel.
- term
- The terminal type. Usually set in ~/.login as described under Startup and shutdown.
- time
- If set to a number, then the time builtin (q.v.) executes automatically after each command which takes more than that many CPU seconds. If there is a second word, it is used as a format string for the output of the time builtin. (u) The following sequences may be used in the format string:
-
- %U
- The time the process spent in user mode in cpu seconds.
- %S
- The time the process spent in kernel mode in cpu seconds.
- %E
- The elapsed (wall clock) time in seconds.
- %P
- The CPU percentage computed as (%U + %S) / %E.
- %W
- Number of times the process was swapped.
- %X
- The average amount in (shared) text space used in Kbytes.
- %D
- The average amount in (unshared) data/stack space used in Kbytes.
- %K
- The total space used (%X + %D) in Kbytes.
- %M
- The maximum memory the process had in use at any time in Kbytes.
- %F
- The number of major page faults (page needed to be brought from disk).
- %R
- The number of minor page faults.
- %I
- The number of input operations.
- %O
- The number of output operations.
- %r
- The number of socket messages received.
- %s
- The number of socket messages sent.
- %k
- The number of signals received.
- %w
- The number of voluntary context switches (waits).
- %c
- The number of involuntary context switches.
Only the first four sequences are supported on systems without BSD resource limit functions. The default time format is `%Uu %Ss %E %P %X+%Dk %I+%Oio %Fpf+%Ww' for systems that support resource usage reporting and `%Uu %Ss %E %P' for systems that do not.
Under Sequent's DYNIX/ptx, %X, %D, %K, %r and %s are not available, but the following additional sequences are:
- %Y
- The number of system calls performed.
- %Z
- The number of pages which are zero-filled on demand.
- %i
- The number of times a process's resident set size was increased by the kernel.
- %d
- The number of times a process's resident set size was decreased by the kernel.
- %l
- The number of read system calls performed.
- %m
- The number of write system calls performed.
- %p
- The number of reads from raw disk devices.
- %q
- The number of writes to raw disk devices.
and the default time format is `%Uu %Ss %E %P %I+%Oio %Fpf+%Ww'. Note that the CPU percentage can be higher than 100% on multi-processors.
- tperiod (+)
- The period, in minutes, between executions of the periodic special alias.
- tty (+)
- The name of the tty, or empty if not attached to one.
- uid (+)
- The user's real user ID.
- user
- The user's login name.
- verbose
- If set, causes the words of each command to be printed, after history substitution (if any). Set by the -v command line option.
- version (+)
- The version ID stamp. It contains the shell's version number (see tcsh), origin, release date, vendor, operating system and machine (see VENDOR, OSTYPE and MACHTYPE) and a comma-separated list of options which were set at compile time. Options which are set by default in the distribution are noted.
-
- 8b
- The shell is eight bit clean; default
- 7b
- The shell is not eight bit clean
- wide
- The shell is multibyte encoding clean (like UTF-8)
- nls
- The system's NLS is used; default for systems with NLS
- lf
- Login shells execute /etc/csh.login before instead of after /etc/csh.cshrc and ~/.login before instead of after ~/.tcshrc and ~/.history.
- dl
- `.' is put last in path for security; default
- nd
- `.' is omitted from path for security
- vi
- vi-style editing is the default rather than emacs
- dtr
- Login shells drop DTR when exiting
- bye
- bye is a synonym for logout and log is an alternate name for watchlog
- al
- autologout is enabled; default
- kan
- Kanji is used if appropriate according to locale settings, unless the nokanji shell variable is set
- sm
- The system's malloc(3) is used
- hb
- The `#!<program> <args>' convention is emulated when executing shell scripts
- ng
- The newgrp builtin is available
- rh
- The shell attempts to set the REMOTEHOST environment variable
- afs
- The shell verifies your password with the kerberos server if local authentication fails. The afsuser shell variable or the AFSUSER environment variable override your local username if set.
An administrator may enter additional strings to indicate differences in the local version.
- visiblebell (+)
- If set, a screen flash is used rather than the audible bell. See also nobeep.
- watch (+)
-
A list of user/terminal pairs to watch for logins and logouts.
If either the user is `any' all terminals are watched for the given user
and vice versa.
Setting watch to `(any any)' watches all users and terminals.
For example,
-
- set watch = (george ttyd1 any console $user any)
reports activity of the user `george' on ttyd1, any user on the console, and oneself (or a trespasser) on any terminal.
Logins and logouts are checked every 10 minutes by default, but the first word of watch can be set to a number to check every so many minutes. For example,
- set watch = (1 any any)
reports any login/logout once every minute. For the impatient, the log builtin command triggers a watch report at any time. All current logins are reported (as with the log builtin) when watch is first set.
The who shell variable controls the format of watch reports.
-
- who (+)
- The format string for watch messages. The following sequences are replaced by the given information:
-
- %n
- The name of the user who logged in/out.
- %a
- The observed action, i.e., `logged on', `logged off' or `replaced olduser on'.
- %l
- The terminal (tty) on which the user logged in/out.
- %M
- The full hostname of the remote host, or `local' if the login/logout was from the local host.
- %m
- The hostname of the remote host up to the first `.'. The full name is printed if it is an IP address or an X Window System display.
%M and %m are available on only systems that store the remote hostname in /etc/utmp. If unset, `%n has %a %l from %m.' is used, or `%n has %a %l.' on systems which don't store the remote hostname.
- wordchars (+)
- A list of non-alphanumeric characters to be considered part of a word by the forward-word, backward-word etc., editor commands. If unset, `*?_-.[]~=' is used.
ENVIRONMENT
- AFSUSER (+)
- Equivalent to the afsuser shell variable.
- COLUMNS
- The number of columns in the terminal. See Terminal management.
- DISPLAY
- Used by X Window System (see X(1)). If set, the shell does not set autologout (q.v.).
- EDITOR
- The pathname to a default editor. See also the VISUAL environment variable and the run-fg-editor editor command.
- GROUP (+)
- Equivalent to the group shell variable.
- HOME
- Equivalent to the home shell variable.
- HOST (+)
- Initialized to the name of the machine on which the shell is running, as determined by the gethostname(2) system call.
- HOSTTYPE (+)
- Initialized to the type of machine on which the shell is running, as determined at compile time. This variable is obsolete and will be removed in a future version.
- HPATH (+)
- A colon-separated list of directories in which the run-help editor command looks for command documentation.
- LANG
- Gives the preferred character environment. See Native Language System support.
- LC_CTYPE
- If set, only ctype character handling is changed. See Native Language System support.
- LINES
- The number of lines in the terminal. See Terminal management.
- LS_COLORS
- The format of this variable is reminiscent of the termcap(5) file format; a colon-separated list of expressions of the form "xx=string", where "xx" is a two-character variable name. The variables with their associated defaults are:
-
-
- no 0
-
Normal (non-filename) text
- fi 0
-
Regular file
- di 01;34
-
Directory
- ln 01;36
-
Symbolic link
- pi 33
-
Named pipe (FIFO)
- so 01;35
-
Socket
- do 01;35
-
Door
- bd 01;33
-
Block device
- cd 01;32
-
Character device
- ex 01;32
-
Executable file
- mi (none)
-
Missing file (defaults to fi)
- or (none)
-
Orphaned symbolic link (defaults to ln)
- lc ^[[
-
Left code
- rc m
-
Right code
- ec (none)
-
End code (replaces lc+no+rc)
You need to include only the variables you want to change from the default.
File names can also be colorized based on filename extension. This is specified in the LS_COLORS variable using the syntax "*ext=string". For example, using ISO 6429 codes, to color all C-language source files blue you would specify "*.c=34". This would color all files ending in .c in blue (34) color.
Control characters can be written either in C-style-escaped notation, or in stty-like ^-notation. The C-style notation adds ^[ for Escape, _ for a normal space character, and ? for Delete. In addition, the ^[ escape character can be used to override the default interpretation of ^[, ^, : and =.
Each file will be written as <lc> <color-code> <rc> <filename> <ec>. If the <ec> code is undefined, the sequence <lc> <no> <rc> will be used instead. This is generally more convenient to use, but less general. The left, right and end codes are provided so you don't have to type common parts over and over again and to support weird terminals; you will generally not need to change them at all unless your terminal does not use ISO 6429 color sequences but a different system.
If your terminal does use ISO 6429 color codes, you can compose the type codes (i.e., all except the lc, rc, and ec codes) from numerical commands separated by semicolons. The most common commands are:
-
- 0
- to restore default color
- 1
- for brighter colors
- 4
- for underlined text
- 5
- for flashing text
- 30
- for black foreground
- 31
- for red foreground
- 32
- for green foreground
- 33
- for yellow (or brown) foreground
- 34
- for blue foreground
- 35
- for purple foreground
- 36
- for cyan foreground
- 37
- for white (or gray) foreground
- 40
- for black background
- 41
- for red background
- 42
- for green background
- 43
- for yellow (or brown) background
- 44
- for blue background
- 45
- for purple background
- 46
- for cyan background
- 47
- for white (or gray) background
Not all commands will work on all systems or display devices.
A few terminal programs do not recognize the default end code properly. If all text gets colorized after you do a directory listing, try changing the no and fi codes from 0 to the numerical codes for your standard fore- and background colors.
-
- MACHTYPE (+)
- The machine type (microprocessor class or machine model), as determined at compile time.
- NOREBIND (+)
- If set, printable characters are not rebound to self-insert-command. See Native Language System support.
- OSTYPE (+)
- The operating system, as determined at compile time.
- PATH
- A colon-separated list of directories in which to look for executables. Equivalent to the path shell variable, but in a different format.
- PWD (+)
- Equivalent to the cwd shell variable, but not synchronized to it; updated only after an actual directory change.
- REMOTEHOST (+)
- The host from which the user has logged in remotely, if this is the case and the shell is able to determine it. Set only if the shell was so compiled; see the version shell variable.
- SHLVL (+)
- Equivalent to the shlvl shell variable.
- SYSTYPE (+)
- The current system type. (Domain/OS only)
- TERM
- Equivalent to the term shell variable.
- TERMCAP
- The terminal capability string. See Terminal management.
- USER
- Equivalent to the user shell variable.
- VENDOR (+)
- The vendor, as determined at compile time.
- VISUAL
- The pathname to a default full-screen editor. See also the EDITOR environment variable and the run-fg-editor editor command.
FILES
- /etc/csh.cshrc
- Read first by every shell. ConvexOS, Stellix and Intel use /etc/cshrc and NeXTs use /etc/cshrc.std. A/UX, AMIX, Cray and IRIX have no equivalent in csh(1), but read this file in tcsh anyway. Solaris 2.x does not have it either, but tcsh reads /etc/.cshrc. (+)
- /etc/csh.login
- Read by login shells after /etc/csh.cshrc. ConvexOS, Stellix and Intel use /etc/login, NeXTs use /etc/login.std, Solaris 2.x uses /etc/.login and A/UX, AMIX, Cray and IRIX use /etc/cshrc.
- ~/.tcshrc (+)
- Read by every shell after /etc/csh.cshrc or its equivalent.
- ~/.cshrc
- Read by every shell, if ~/.tcshrc doesn't exist, after /etc/csh.cshrc or its equivalent. This manual uses `~/.tcshrc' to mean `~/.tcshrc or, if ~/.tcshrc is not found, ~/.cshrc'.
- ~/.history
- Read by login shells after ~/.tcshrc if savehist is set, but see also histfile.
- ~/.login
- Read by login shells after ~/.tcshrc or ~/.history. The shell may be compiled to read ~/.login before instead of after ~/.tcshrc and ~/.history; see the version shell variable.
- ~/.cshdirs (+)
- Read by login shells after ~/.login if savedirs is set, but see also dirsfile.
- /etc/csh.logout
- Read by login shells at logout. ConvexOS, Stellix and Intel use /etc/logout and NeXTs use /etc/logout.std. A/UX, AMIX, Cray and IRIX have no equivalent in csh(1), but read this file in tcsh anyway. Solaris 2.x does not have it either, but tcsh reads /etc/.logout. (+)
- ~/.logout
- Read by login shells at logout after /etc/csh.logout or its equivalent.
- /bin/sh
- Used to interpret shell scripts not starting with a `#'.
- /tmp/sh*
- Temporary file for `<<'.
- /etc/passwd
- Source of home directories for `~name' substitutions.
The order in which startup files are read may differ if the shell was so compiled; see Startup and shutdown and the version shell variable.
NEW FEATURES (+)
This manual describes tcsh as a single entity, but experienced csh(1) users will want to pay special attention to tcsh's new features.A command-line editor, which supports GNU Emacs or vi(1)-style key bindings. See The command-line editor and Editor commands.
Programmable, interactive word completion and listing. See Completion and listing and the complete and uncomplete builtin commands.
Spelling correction (q.v.) of filenames, commands and variables.
Editor commands (q.v.) which perform other useful functions in the middle of typed commands, including documentation lookup (run-help), quick editor restarting (run-fg-editor) and command resolution (which-command).
An enhanced history mechanism. Events in the history list are time-stamped. See also the history command and its associated shell variables, the previously undocumented `#' event specifier and new modifiers under History substitution, the *-history, history-search-*, i-search-*, vi-search-* and toggle-literal-history editor commands and the histlit shell variable.
Enhanced directory parsing and directory stack handling. See the cd, pushd, popd and dirs commands and their associated shell variables, the description of Directory stack substitution, the dirstack, owd and symlinks shell variables and the normalize-command and normalize-path editor commands.
Negation in glob-patterns. See Filename substitution.
New File inquiry operators (q.v.) and a filetest builtin which uses them.
A variety of Automatic, periodic and timed events (q.v.) including scheduled events, special aliases, automatic logout and terminal locking, command timing and watching for logins and logouts.
Support for the Native Language System (see Native Language System support), OS variant features (see OS variant support and the echo_style shell variable) and system-dependent file locations (see FILES).
Extensive terminal-management capabilities. See Terminal management.
New builtin commands including builtins, hup, ls-F, newgrp, printenv, which and where (q.v.).
New variables that make useful information easily available to the shell. See the gid, loginsh, oid, shlvl, tcsh, tty, uid and version shell variables and the HOST, REMOTEHOST, VENDOR, OSTYPE and MACHTYPE environment variables.
A new syntax for including useful information in the prompt string (see prompt). and special prompts for loops and spelling correction (see prompt2 and prompt3).
Read-only variables. See Variable substitution.
BUGS
When a suspended command is restarted, the shell prints the directory it started in if this is different from the current directory. This can be misleading (i.e., wrong) as the job may have changed directories internally.Shell builtin functions are not stoppable/restartable. Command sequences of the form `a ; b ; c' are also not handled gracefully when stopping is attempted. If you suspend `b', the shell will then immediately execute `c'. This is especially noticeable if this expansion results from an alias. It suffices to place the sequence of commands in ()'s to force it to a subshell, i.e., `( a ; b ; c )'.
Control over tty output after processes are started is primitive; perhaps this will inspire someone to work on a good virtual terminal interface. In a virtual terminal interface much more interesting things could be done with output control.
Alias substitution is most often used to clumsily simulate shell procedures; shell procedures should be provided rather than aliases.
Commands within loops are not placed in the history list. Control structures should be parsed rather than being recognized as built-in commands. This would allow control commands to be placed anywhere, to be combined with `|', and to be used with `&' and `;' metasyntax.
foreach doesn't ignore here documents when looking for its end.
It should be possible to use the `:' modifiers on the output of command substitutions.
The screen update for lines longer than the screen width is very poor if the terminal cannot move the cursor up (i.e., terminal type `dumb').
HPATH and NOREBIND don't need to be environment variables.
Glob-patterns which do not use `?', `*' or `[]' or which use `{}' or `~' are not negated correctly.
The single-command form of if does output redirection even if the expression is false and the command is not executed.
ls-F includes file identification characters when sorting filenames and does not handle control characters in filenames well. It cannot be interrupted.
Command substitution supports multiple commands and conditions, but not cycles or backward gotos.
Report bugs at http://bugs.gw.com/, preferably with fixes. If you want to help maintain and test tcsh, send mail to<EMAIL_ADDRESS>with the text `subscribe tcsh' on a line by itself in the body.
THE T IN TCSH
In 1964, DEC produced the PDP-6. The PDP-10 was a later re-implementation. It was re-christened the DECsystem-10 in 1970 or so when DEC brought out the second model, the KI10.TENEX was created at Bolt, Beranek & Newman (a Cambridge, Massachusetts think tank) in 1972 as an experiment in demand-paged virtual memory operating systems. They built a new pager for the DEC PDP-10 and created the OS to go with it. It was extremely successful in academia.
In 1975, DEC brought out a new model of the PDP-10, the KL10; they intended to have only a version of TENEX, which they had licensed from BBN, for the new box. They called their version TOPS-20 (their capitalization is trademarked). A lot of TOPS-10 users (`The OPerating System for PDP-10') objected; thus DEC found themselves supporting two incompatible systems on the same hardware--but then there were 6 on the PDP-11!
TENEX, and TOPS-20 to version 3, had command completion via a user-code-level subroutine library called ULTCMD. With version 3, DEC moved all that capability and more into the monitor (`kernel' for you Unix types), accessed by the COMND% JSYS (`Jump to SYStem' instruction, the supervisor call mechanism [are my IBM roots also showing?]).
The creator of tcsh was impressed by this feature and several others of TENEX and TOPS-20, and created a version of csh which mimicked them.
LIMITATIONS
The system limits argument lists to ARG_MAX characters.The number of arguments to a command which involves filename expansion is limited to 1/6th the number of characters allowed in an argument list.
Command substitutions may substitute no more characters than are allowed in an argument list.
To detect looping, the shell restricts the number of alias substitutions on a single line to 20.
SEE ALSO
csh(1), emacs(1), ls(1), newgrp(1), sh(1), setpath(1), stty(1), su(1), tset(1), vi(1), x(1), access(2), execve(2), fork(2), killpg(2), pipe(2), setrlimit(2), sigvec(2), stat(2), umask(2), vfork(2), wait(2), malloc(3), setlocale(3), tty(4), a.out(5), termcap(5), environ(7), termio(7), Introduction to the C ShellVERSION
This manual documents tcsh 6.17.00 (Astron) 2009-07-10.AUTHORS
- William Joy
- Original author of csh(1)
- J.E. Kulp, IIASA, Laxenburg, Austria
- Job control and directory stack features
- Ken Greer, HP Labs, 1981
- File name completion
- Mike Ellis, Fairchild, 1983
- Command name recognition/completion
- Paul Placeway, Ohio State CIS Dept., 1983-1993
- Command line editor, prompt routines, new glob syntax and numerous fixes and speedups
- Karl Kleinpaste, CCI 1983-4
- Special aliases, directory stack extraction stuff, login/logout watch, scheduled events, and the idea of the new prompt format
- Rayan Zachariassen, University of Toronto, 1984
- ls-F and which builtins and numerous bug fixes, modifications and speedups
- Chris Kingsley, Caltech
- Fast storage allocator routines
- Chris Grevstad, TRW, 1987
- Incorporated 4.3BSD csh into tcsh
- Christos S. Zoulas, Cornell U. EE Dept., 1987-94
- Ports to HPUX, SVR2 and SVR3, a SysV version of getwd.c, SHORT_STRINGS support and a new version of sh.glob.c
- James J Dempsey, BBN, and Paul Placeway, OSU, 1988
- A/UX port
- Daniel Long, NNSC, 1988
- wordchars
- Patrick Wolfe, Kuck and Associates, Inc., 1988
- vi mode cleanup
- David C Lawrence, Rensselaer Polytechnic Institute, 1989
- autolist and ambiguous completion listing
- Alec Wolman, DEC, 1989
- Newlines in the prompt
- Matt Landau, BBN, 1989
- ~/.tcshrc
- Ray Moody, Purdue Physics, 1989
- Magic space bar history expansion
- Mordechai ????, Intel, 1989
- printprompt() fixes and additions
- Kazuhiro Honda, Dept. of Computer Science, Keio University, 1989
- Automatic spelling correction and prompt3
- Per Hedeland, Ellemtel, Sweden, 1990-
- Various bugfixes, improvements and manual updates
- Hans J. Albertsson (Sun Sweden)
- ampm, settc and telltc
- Michael Bloom
- Interrupt handling fixes
- Michael Fine, Digital Equipment Corp
- Extended key support
- Eric Schnoebelen, Convex, 1990
- Convex support, lots of csh bug fixes, save and restore of directory stack
- Ron Flax, Apple, 1990
- A/UX 2.0 (re)port
- Dan Oscarsson, LTH Sweden, 1990
- NLS support and simulated NLS support for non NLS sites, fixes
- Johan Widen, SICS Sweden, 1990
- shlvl, Mach support, correct-line, 8-bit printing
- Matt Day, Sanyo Icon, 1990
- POSIX termio support, SysV limit fixes
- Jaap Vermeulen, Sequent, 1990-91
- Vi mode fixes, expand-line, window change fixes, Symmetry port
- Martin Boyer, Institut de recherche d'Hydro-Quebec, 1991
- autolist beeping options, modified the history search to search for the whole string from the beginning of the line to the cursor.
- Scott Krotz, Motorola, 1991
- Minix port
- David Dawes, Sydney U. Australia, Physics Dept., 1991
- SVR4 job control fixes
- Jose Sousa, Interactive Systems Corp., 1991
- Extended vi fixes and vi delete command
- Marc Horowitz, MIT, 1991
- ANSIfication fixes, new exec hashing code, imake fixes, where
- Bruce Sterling Woodcock<EMAIL_ADDRESS>1991-1995
- ETA and Pyramid port, Makefile and lint fixes, ignoreeof=n addition, and various other portability changes and bug fixes
- Jeff Fink, 1992
- complete-word-fwd and complete-word-back
- Harry C. Pulley, 1992
- Coherent port
- Andy Phillips, Mullard Space Science Lab U.K., 1992
- VMS-POSIX port
- Beto Appleton, IBM Corp., 1992
- Walking process group fixes, csh bug fixes, POSIX file tests, POSIX SIGHUP
- Scott Bolte, Cray Computer Corp., 1992
- CSOS port
- Kaveh R. Ghazi, Rutgers University, 1992
- Tek, m88k, Titan and Masscomp ports and fixes. Added autoconf support.
- Mark Linderman, Cornell University, 1992
- OS/2 port
- Mika Liljeberg<EMAIL_ADDRESS>1992
- Linux port
- Tim P. Starrin, NASA Langley Research Center Operations, 1993
- Read-only variables
- Dave Schweisguth, Yale University, 1993-4
- New man page and tcsh.man2html
- Larry Schwimmer, Stanford University, 1993
- AFS and HESIOD patches
- Luke Mewburn, RMIT University, 1994-6
- Enhanced directory printing in prompt, added ellipsis and rprompt.
- Edward Hutchins, Silicon Graphics Inc., 1996
- Added implicit cd.
- Martin Kraemer, 1997
- Ported to Siemens Nixdorf EBCDIC machine
- Amol Deshpande, Microsoft, 1997
- Ported to WIN32 (Windows/95 and Windows/NT); wrote all the missing library and message catalog code to interface to Windows.
- Taga Nayuta, 1998
- Color ls additions.
THANKS TO
Bryan Dunlap, Clayton Elwell, Karl Kleinpaste, Bob Manson, Steve Romig, Diana Smetters, Bob Sutterfield, Mark Verber, Elizabeth Zwicky and all the other people at Ohio State for suggestions and encouragementAll the people on the net, for putting up with, reporting bugs in, and suggesting new additions to each and every version
Richard M. Alderson III, for writing the `T in tcsh' section
Index
- NAME
- SYNOPSIS
- DESCRIPTION
-
- Argument list processing
- Startup and shutdown
- Editing
- The command-line editor (+)
- Completion and listing (+)
- Spelling correction (+)
- Editor commands (+)
- Lexical structure
- Substitutions
- History substitution
- Alias substitution
- Variable substitution
- Command, filename and directory stack substitution
- Command substitution
- Filename substitution
- Directory stack substitution (+)
- Other substitutions (+)
- Commands
- Simple commands, pipelines and sequences
- Builtin and non-builtin command execution
- Input/output
- Features
- Control flow
- Expressions
- Logical, arithmetical and comparison operators
- Command exit status
- File inquiry operators
- Jobs
- Status reporting
- Automatic, periodic and timed events (+)
- Native Language System support (+)
- OS variant support (+)
- Signal handling
- Terminal management (+)
- REFERENCE
- ENVIRONMENT
- FILES
- NEW FEATURES (+)
- BUGS
- THE T IN TCSH
- LIMITATIONS
- SEE ALSO
- VERSION
- AUTHORS
- THANKS TO
This document was created by man2html, using the manual pages.
Time: 05:29:02 GMT, December 24, 2015


Colin Kaepernick Supporters Show Up In Polaris Slingshot’s & Greatly Outnumber Protesters In Atlanta (VIDEO)
by Darrelle LincolnColin Kaepernick is in Atlanta today to try out for NFL teams in an attempt to show that he still has something left in the tank after being out for three seasons, largely due to the controversy surrounding his Anthem protests.
Aside from him being in Atlanta were a few protesters who came to the Falcons practice facility to have their voices heard.
Those protestors were met with even more supporters who made sure to show their faces as well and their group was even bigger as many showed up rocking the ever popular Poaris Slingshot.


Free home delivery
Provide free home delivery for all product over $100
Provide free home delivery for all product over $100
We ensure the product quality that is our main goal
Return product within 3 days for any product you buy
We ensure the product quality that you can trust easily


For a full VR experience, use
Google Chrome WebVR build
with Ocullus Rift or mobile browser with a
Google Cardboard


Seer Skahi:
Everywhere there are signs of the approaching endless winter. My heart is grieved for the future of my people!
Youngster, what will you do when the end comes?
Learn skills.
Ask about Skill Enchanting.
Quest


Question
Multiple threads can publish and receive each other’s message:
whenever a thread publishes a message, all the other threads can receive and print out that message;
if multiple message get published, the messages should be queued or whatever recorded and other threads can print out the message one by one;
no published message should be missed by any other threads.
Solution
Suggested by level 13:
给每个thread分一个blocking queue就完了。这题延伸开来是个很好的设计题, pubsub, messaging framework etc.
Using a blocking queue to store messages for each server. It’s pretty much like consumer-producer. But here, the server takes on both roles. Read my code below, or [Java OOP] PubSub (Publish–subscribe) pattern to learn about PubSub.
Code
Below is my code, it may not be the correct solution. If you would like to discuss, please leave me a comment!
public class MessagingServer implements Runnable {
String serverId;
List<MessagingServer> servers;
BlockingQueue<String> messages;
boolean isFinished;
public MessagingServer(String id, List<MessagingServer> list, int qSize) {
this.serverId = id;
this.servers = list;
messages = new ArrayBlockingQueue<String>(qSize);
isFinished = false;
}
public void run() {
// this would be the consumer
// everything that is added to BlockingQueue<String> messages is printed
while (!isFinished) {
String msg;
try {
msg = messages.take();
System.out.println(serverId + " says: " + msg);
} catch (InterruptedException e) {
e.printStackTrace();
}
}
}
public void sendMessage(String msg) {
// this is the producer
// insert this msg in the blockingQ of all other servers
for (MessagingServer server : servers) {
server.messages.add(msg + " (received from " + this.serverId + ")");
}
}
public void terminate() {
this.isFinished = true;
}
}


Coding is my life
I'm Yao Xiao
Hi, My name is Yao Xiao. I am currently full-time M.S Computer Science student at Northeastern Univeristy.I have undergraduate degree in Accounting and Finance, which is a totally different field to computer science. However,computer science takes me to a brand-new world. I enjoy working out problems step by step. Computer Science is a field that requires people organize algorithm and then put the theory into code. I am really into process of coding.I am not an "outdoor" guy, my greastest hobbies are watching TV drama and playing online games.


Faux Hollows Solver
Working on developing color palettes for color blind accessibility. Added tool tips for the mean time. Please contact me with any other accessibility issues.
Instructions
Note: "2x2" is synonymous with "Coffer" or "Gift Box", and "Bias" is synonymous with "orientation".
Select a box type from the top of the left side bar.
Click on a box to apply the selected type.
Select a strategy and set weight values.
Click "Apply" to calculate the next move if live updates are off.
Yellow boxes indicate the best current choice based on strategy.
When swords are uncovered, the graphic can be used to determine it's full location, or just it's orientation, or just don't bother.
If only the orientation is determined, check either the vertical or horizontal bias.
When 2x2 is uncovered, use the graphic to determine if it's a Coffer or a Gift Box.
Note: Weights only apply to "Weighted" strategy.
Suggestion: If using weights, change the swords weight to 15 after a retelling.
About
This is an attempt at making a statistical approach to to the Faux Hollows minigame that released in 5.3.
Now that the minigame has been released, a number of assumptions were confirmed. Except for one:
The fox will ALWAYS appear.
This has since proven not to be the case. The fox is not guaranteed to appear. As such, additional strategies have been added. These are listed under "No Fox" in the Strategies section.
The exact chance that the Fox will appear is not known, at least to me. If anyone should know this information, please contact me through one of the avenues below.
Minor disclaimer
This calculator will NOT guarantee anything. Not a single reward is guaranteed for using this tool. What it provides is a statistical advantage. Even statistics, by it's nature, is falliable.
Also, this is my first forray into web programming. If something breaks, send me a DM on Discord at Sturalke#0249 or on Reddit at u/Sturalke. I'll do what I can to figure out what went wrong.
Created by Fyrin Niyuun on Faerie. GitHub


Answer a few questions and receive your personalized travel recommendation.

The Vacation Robot suggests that children should not drink coffee!
The Vacation Robot would like to remind you that you will probably not be doing any solo travel for a few years -- you're probably going wherever your parents go!
The Vacation Robot would like to request that you exercise caution when participating in these sports at your age!
The Vacation Robot recommends that you might want to think about retiring in lovely Ashland, Oregon!
Click for more info about AshlandThe Vacation Robot recommends that you visit lovely !


#canvas{ box-shadow: 10px 10px 10px blue; } #wrapper{ box-shadow: 10px 10px 10px blue; }
Use keyboard arrows to control the space craft and score as many points as possible by shooting up meteors and enemies.Do not get hit or touched by laser rocks and space ships.
You are thunder class thunderbird fighter and have the latest space ship that has shield and has extra fast ball laser shooter that changes to a normal when you pick up the fast shooting bonusand can withstand 3 laser shots
The pink space ship is assault class pink fighter made to destroy war class space ship and they return fire
The red space ship is sentry class red fighter basically a space cannon strong enough to pulverize the shield health to half
The green space ship is a scout class green landmine that can only fly forward (usually) made to destroy any ally ship it touches and it is drone
The red/blue is a dragon class kamekaze that is a heat seeking mine which can also be controlled as drone or just left in a mine field
Score:


--- inscription: http://register.uxlausanne.com/ adresse: "Arsenic\r\nRue de Genève 57\r\n1004 Lausanne" datemeeting: 22-23 May 2014 adresse-gmaps: https://www.google.ch/maps/place/Fondation+Arsenic/@46.522548,6.621756,17z/data=!3m1!4b1!4m2!3m1!1s0x0:0xbbb327a9fa627008 number: '' event_date: '' speaker: '' layout: post status: publish published: true title: UX Lausanne 2014 author: display_name: Simon Farine login: simon_bricolo email<EMAIL_ADDRESS>url: '' author_login: simon_bricolo author_email<EMAIL_ADDRESS>excerpt: 22-23 May 2014 - Creating delightful User Experiences - 2 days - 8 talks - 8 workshops wordpress_id: 734 wordpress_url: http://uxromandie.ch/?p=734 date: '2014-05-14 13:05:57 +0200' date_gmt: '2014-05-14 13:05:57 +0200' categories: - événements tags: - Conférence - uxlausanne comments: [] ---
UX Lausanne is a 2 days conference in Lausanne, Switzerland, on creating delightful User Experiences.
After 2 years of monthly UX Romandie meetups, UX Lausanne will take place for the first time in 2014. The 2 days’ format will bring together local & international UX professionals to share knowledge and gain expertise in the User Experience field. The conference will be held at Arsenic Theater, one of Lausanne's most vibrant cultural spot.
UX Lausanne is the first Western Switzerland event dedicated exclusively to User Experience Design. We look forward to connect you with some of the most influential UX practitioners, leading thinkers, talented developers and innovative designers.


Add a new store location
Add Store Name Location:
Add Minimum Customers:
Add Maximum Customers:
Add Average Cookies per Hour:
Add New Store Information


module NMatrix::LAPACK
Public Class Methods
alloc_svd_result(matrix)
click to toggle source
# File lib/nmatrix/lapack_core.rb, line 77 def alloc_svd_result(matrix) [ NMatrix.new(matrix.shape[0], dtype: matrix.dtype), NMatrix.new([[matrix.shape[0],matrix.shape[1]].min,1], dtype: matrix.abs_dtype), NMatrix.new(matrix.shape[1], dtype: matrix.dtype) ] end
clapack_getri(order, n, a, lda, ipiv)
click to toggle source
# File lib/nmatrix/lapack_core.rb, line 176 def clapack_getri(order, n, a, lda, ipiv) raise(NotImplementedError,"clapack_getri requires the nmatrix-atlas gem") end
clapack_potrf(order, uplo, n, a, lda)
click to toggle source
# File lib/nmatrix/lapack_core.rb, line 164 def clapack_potrf(order, uplo, n, a, lda) raise(NotImplementedError,"clapack_potrf requires the nmatrix-atlas gem") end
clapack_potri(order, uplo, n, a, lda)
click to toggle source
# File lib/nmatrix/lapack_core.rb, line 168 def clapack_potri(order, uplo, n, a, lda) raise(NotImplementedError,"clapack_potri requires the nmatrix-atlas gem") end
clapack_potrs(order, uplo, n, nrhs, a, lda, b, ldb)
click to toggle source
# File lib/nmatrix/lapack_core.rb, line 172 def clapack_potrs(order, uplo, n, nrhs, a, lda, b, ldb) raise(NotImplementedError,"clapack_potrs requires the nmatrix-atlas gem") end
geev(matrix, which=:both)
click to toggle source
# File lib/nmatrix/atlas.rb, line 77 def geev(matrix, which=:both) raise(StorageTypeError, "LAPACK functions only work on dense matrices") unless matrix.dense? raise(ShapeError, "eigenvalues can only be computed for square matrices") unless matrix.dim == 2 && matrix.shape[0] == matrix.shape[1] jobvl = (which == :both || which == :left) ? :t : false jobvr = (which == :both || which == :right) ? :t : false n = matrix.shape[0] # Outputs eigenvalues = NMatrix.new([n, 1], dtype: matrix.dtype) # For real dtypes this holds only the real part of the eigenvalues. imag_eigenvalues = matrix.complex_dtype? ? nil : NMatrix.new([n, 1], dtype: matrix.dtype) # For complex dtypes, this is unused. left_output = jobvl ? matrix.clone_structure : nil right_output = jobvr ? matrix.clone_structure : nil # lapack_geev is a pure LAPACK routine so it expects column-major matrices, # so we need to transpose the input as well as the output. temporary_matrix = matrix.transpose NMatrix::LAPACK::lapack_geev(jobvl, # compute left eigenvectors of A? jobvr, # compute right eigenvectors of A? (left eigenvectors of A**T) n, # order of the matrix temporary_matrix,# input matrix (used as work) n, # leading dimension of matrix eigenvalues,# real part of computed eigenvalues imag_eigenvalues,# imag part of computed eigenvalues left_output, # left eigenvectors, if applicable n, # leading dimension of left_output right_output, # right eigenvectors, if applicable n, # leading dimension of right_output 2*n) left_output = left_output.transpose if jobvl right_output = right_output.transpose if jobvr # For real dtypes, transform left_output and right_output into correct forms. # If the j'th and the (j+1)'th eigenvalues form a complex conjugate # pair, then the j'th and (j+1)'th columns of the matrix are # the real and imag parts of the eigenvector corresponding # to the j'th eigenvalue. if !matrix.complex_dtype? complex_indices = [] n.times do |i| complex_indices << i if imag_eigenvalues[i] != 0.0 end if !complex_indices.empty? # For real dtypes, put the real and imaginary parts together eigenvalues = eigenvalues + imag_eigenvalues*Complex(0.0,1.0) left_output = left_output.cast(dtype: NMatrix.upcast(:complex64, matrix.dtype)) if left_output right_output = right_output.cast(dtype: NMatrix.upcast(:complex64, matrix.dtype)) if right_output end complex_indices.each_slice(2) do |i, _| if right_output right_output[0...n,i] = right_output[0...n,i] + right_output[0...n,i+1]*Complex(0.0,1.0) right_output[0...n,i+1] = right_output[0...n,i].complex_conjugate end if left_output left_output[0...n,i] = left_output[0...n,i] + left_output[0...n,i+1]*Complex(0.0,1.0) left_output[0...n,i+1] = left_output[0...n,i].complex_conjugate end end end if which == :both return [eigenvalues, left_output, right_output] elsif which == :left return [eigenvalues, left_output] else return [eigenvalues, right_output] end end
gesdd(matrix, workspace_size=nil)
click to toggle source
# File lib/nmatrix/atlas.rb, line 166 def gesdd(matrix, workspace_size=nil) min_workspace_size = matrix.shape.min * (6 + 4 * matrix.shape.min) + matrix.shape.max workspace_size = min_workspace_size if workspace_size.nil? || workspace_size < min_workspace_size result = alloc_svd_result(matrix) m = matrix.shape[0] n = matrix.shape[1] # This is a pure LAPACK function so it expects column-major functions. # So we need to transpose the input as well as the output. matrix = matrix.transpose NMatrix::LAPACK::lapack_gesdd(:a, m, n, matrix, m, result[1], result[0], m, result[2], n, workspace_size) result[0] = result[0].transpose result[2] = result[2].transpose result end
gesvd(matrix, workspace_size=1)
click to toggle source
# File lib/nmatrix/atlas.rb, line 151 def gesvd(matrix, workspace_size=1) result = alloc_svd_result(matrix) m = matrix.shape[0] n = matrix.shape[1] # This is a pure LAPACK function so it expects column-major functions. # So we need to transpose the input as well as the output. matrix = matrix.transpose NMatrix::LAPACK::lapack_gesvd(:a, :a, m, n, matrix, m, result[1], result[0], m, result[2], n, workspace_size) result[0] = result[0].transpose result[2] = result[2].transpose result end
lapack_geev(jobvl, jobvr, n, a, lda, w, wi, vl, ldvl, vr, ldvr, lwork)
click to toggle source
# File lib/nmatrix/lapack_core.rb, line 160 def lapack_geev(jobvl, jobvr, n, a, lda, w, wi, vl, ldvl, vr, ldvr, lwork) raise(NotImplementedError,"lapack_geev requires the nmatrix-atlas gem") end
lapack_gesdd(jobz, m, n, a, lda, s, u, ldu, vt, ldvt, lwork)
click to toggle source
# File lib/nmatrix/lapack_core.rb, line 156 def lapack_gesdd(jobz, m, n, a, lda, s, u, ldu, vt, ldvt, lwork) raise(NotImplementedError,"lapack_gesdd requires the nmatrix-atlas gem") end
lapack_gesvd(jobu, jobvt, m, n, a, lda, s, u, ldu, vt, ldvt, lwork)
click to toggle source
The following are functions that used to be implemented in C, but now require nmatrix-atlas to run properly, so we can just implemented their stubs in Ruby.
# File lib/nmatrix/lapack_core.rb, line 152 def lapack_gesvd(jobu, jobvt, m, n, a, lda, s, u, ldu, vt, ldvt, lwork) raise(NotImplementedError,"lapack_gesvd requires the nmatrix-atlas gem") end
laswp(matrix, ipiv)
click to toggle source
laswp(matrix, ipiv) -> NMatrix
Permute the columns of a matrix (in-place) according to the Array ipiv
.
# File lib/nmatrix/lapack_core.rb, line 69 def laswp(matrix, ipiv) raise(ArgumentError, "expected NMatrix for argument 0") unless matrix.is_a?(NMatrix) raise(StorageTypeError, "LAPACK functions only work on :dense NMatrix instances") unless matrix.stype == :dense raise(ArgumentError, "expected Array ipiv to have no more entries than NMatrix a has columns") if ipiv.size > matrix.shape[1] clapack_laswp(matrix.shape[0], matrix, matrix.shape[1], 0, ipiv.size-1, ipiv, 1) end
posv(uplo, a, b)
click to toggle source
# File lib/nmatrix/atlas.rb, line 59 def posv(uplo, a, b) raise(ShapeError, "a must be square") unless a.dim == 2 && a.shape[0] == a.shape[1] raise(ShapeError, "number of rows of b must equal number of cols of a") unless a.shape[1] == b.shape[0] raise(StorageTypeError, "only works with dense matrices") unless a.stype == :dense && b.stype == :dense raise(DataTypeError, "only works for non-integer, non-object dtypes") if a.integer_dtype? || a.object_dtype? || b.integer_dtype? || b.object_dtype? x = b.clone clone = a.clone n = a.shape[0] nrhs = b.shape[1] clapack_potrf(:row, uplo, n, clone, n) # Must transpose b before and after: http://math-atlas.sourceforge.net/faq.html#RowSolve x = x.transpose clapack_potrs(:row, uplo, n, nrhs, clone, n, x, n) x.transpose end


June Web browser stats: Rapid Release edition
June brought the first result of Mozilla's new Rapid Release strategy for Firefox. Firefox 4, just three months old, was superceded by the all-new but not-too-different Firefox 5. Firefox's market growth was all but ended by the release of Chrome, and Mozilla is hoping that by adopting a similar release schedule to Google, it will be able to reignite the growth of its user base.
Internet Explorer is down 0.59 points at 53.68 percent. Firefox is essentially unchanged, down 0.04 points to 21.67 percent. Chrome is up 0.59 points to 13.11 percent. Safari is also up, gaining 0.2 points to reach 7.48 percent. Opera dropped 0.3 points to 1.73 percent.
The trends established over the last few months are continuing: Firefox is treading water, while Internet Explorer is losing users, which seem to be being picked up by Chrome. In the past two months, Opera has dropped 0.41 points—that's a loss representing 20% of its market share. Our own Ryan Paul liked Opera 11.50, which was released just a couple of days ago, so perhaps this will help turn around a perilous slide.
Looking at individual versions, Internet Explorer 6, 7, and 8 are all down, by 0.18, 0.46, and 1.21 points respectively. Internet Explorer 9 made strong gains, of 1.44 points, but not enough to undo the losses. Internet Explorer 9's gains seem to be occurring at the expense of older versions—Internet Explorer 8 on Windows 7, versions 7 and 8 on Windows Vista—rather than making converts of the other browsers.
Internet Explorer 9 is of course at something of a disadvantage, as it won't run on Windows XP. While we agree with the decision to cut Windows XP off, one consequence is that not a single Internet Explorer 6 user can upgrade to Internet Explorer 9. Nor can anyone using Internet Explorer 7 or 8 on Windows XP. If the focus is narrowed from all users to just those using Windows 7, the Internet Explorer 9 situation looks a little more promising. Though Internet Explorer 8, which ships with Windows 7, commands the highest market share, at 38.47 percent of Windows 7 users, Internet Explorer 9 takes second place, at 15.61 percent—putting it ahead of Firefox 4 and Chrome 12, at 13.74 and 11.60 percent, respectively.
Internet Explorer 9 seems, therefore, to be performing well among users of Microsoft's latest and greatest operating system; it's just that only 27 percent of the global audience is running that platform. Windows XP still commands a slim majority, with a global share of 51 percent. As Windows XP declines and Windows 7 grows, we can expect to see Internet Explorer 9 lifted by this transition.
Firefox versions 3.5 and 3.6 both saw drops last month, by 2.06 and 0.28 points, respectively, and versions 4 and 5 rose by 0.38 and 2.05 points, respectively. This suggests that the transition from "old" Firefox (3.x) to "modern" Firefox (4 and 5) is slowing down; in May, the 3.x versions dropped by an aggregate of more than 4.5 points, with the then-current Firefox 4 picking up all of those users. This month, only around half as many users made the switch. Though "modern" Firefox versions are now used by a majority of Firefox users, it looks like a hard core of "old" users is going to stick around. Over the next few months, we can expect Firefox 3.5 to decline more heavily, as Mozilla intends to push out a patch that will upgrade users to the newest 3.6 version.
Chrome as ever shows rapid migration between versions. Over the course of June, the browser's stable version went from 11 to 12, and the rapid cutover we've grown to expect occurred. However, that transition isn't complete. 1.39 percent of users are on Chrome 10 or older, and it looks like Google's generally seamless automatic upgrades aren't touching these users. The source of these users isn't clear, though there a few plausible explanations. Obviously, some individuals and corporate users may simply have opted to disable the updates. Automatic updating is the default, but it can be turned off. Though this gives these users and enterprises greater control over the browser version they're using, this comes at some risk; Google doesn't have security updates for old versions of Chrome, so these people are using browsers with known exploitable flaws.
Chrome's automatic updating is also dependent on a system service. Though the browser can be installed by non-administrators, installation of the service requires administrator privileges. Unlike Firefox, which checks for and performs updates within the browser itself, Chrome depends on its service to do this task. If the service doesn't exist, updates don't happen.
That's probably not enough to account for every legacy Chrome user, however. To do that, we probably have to look towards the East Asian market. A long-standing feature of various markets in the region, most notably China and South Korea, is the entrenchment of Internet Explorer, variously attributed to legal mandates (especially in South Korea, where until last year a specific ActiveX control was required for online banking) and widespread software piracy making users reluctant to use Windows Update (even though Internet Explorer upgrades are available to pirated copies of the operating system).
To support this market, a range of browsers based on Internet Explorer's rendering engine, but with substantially greater features, sprung up. The most popular of these are 360 Secure Browser with about 19 percent share of the Chinese market, and Sogou high speed browser, with a little under 6 percent. Though these browsers originally just used the Trident engine that powers Internet Explorer, recent versions extend this by also embedding Chrome. In so doing, they give their users a choice between a relatively modern Chrome browser engine, and the older Internet Explorer engine needed for compatibility. Conceptually, this is very similar to software like Chrome Frame, that allows Internet Explorer users to use Chrome for some browser tabs.
These dual-engine browsers tend to modify Chrome in several ways, one of which is that they exclude Google's automatic update service. They also tend to embed stale versions of Chrome; the current Sogou uses Chrome 6. The result is that users of these browsers, who may well prefer using Chrome for day-to-day browsing, will be stuck with obsolete versions of the browser. And because of the way they're using Chrome, they're out of reach of Google's update system.
The net result of these various usage scenarios is that Chrome's non-upgrading userbase is likely to grow ever larger, with ten percent of Chrome users, and climbing, sticking with versions of the browser that are no longer supported.
Ars' audience continues to show marked differences from the Internet's norms. Firefox, Safari, Internet Explorer, and Opera all saw drops, of 0.94, 0.37, 0.04, and 0.10 points respectively; Chrome saw gains of 0.88 points, with the remainder of the difference picked up by "other."
User comments


Group: A B C D
Sorry, we can't refresh the page. Please try again.
Sorry, we can't show more at the moment. Please try again later.
Tell us what you think about this page


Vehicle Information
Vehicle View
Vehicle View with Map
Vehicle information
Vehicle I/O List
Section 2
Content 2
Section 3
Content 3