- Do you own a home?
- Is your household income at least $2,000 per month?
*You don’t have to spend a dime with the right home warranty coverage.
 When something goes wrong, it can be a big deal! Not to worry you,but you need to be ready for all of the potential damages that may occur to your home and belongings.
DAMAGES TO YOUR HOME ARE UNAVOIDABLE...
- Depending on your geographical location, issues with your AC or heater unit may cause you to grow frustrated with the place that you call home.
- As a homeowner, it is important that you stay protected from unforeseeable damages that may occur to your home.
- Most home insurance policies cover major perils that may occur such as fires, hails, property crimes, and certain types of water damage, it is not the same thing as home warranty
Easy American Home Warranty partners with industry leaders to help customers protect their homes and budget with fast and reliable assistance.
Protection That Is Guaranteed
Quisque imperdiet augue sed elit convallis, at auctor velit aliquam. Proin luctus ligula in quam ultrices dapibus. Aliquam vel turpis ac est molestie dignissim id sed quam. Fusce eleifend congue pharetra. Praesent hendrerit tempor eros quam ultrices dapibus.
Proin luctus ligula in quam ultrices dapibus. Aliquam vel turpis ac est molestie dignissim id sed quam. Fusce eleifend congue pharetra. Praesent hendrerit tempor eros.
Easy American Home Warranty
We partner with industry leaders to help customers protect their homes and budget with fast and reliable assistance.
Easy American Home Warranty
WHAT IS REQUIRED TO QUALIFY?
Benefits of Easy American Home Warranty
Protect against unforeseen repair costs:
damages that happen to your home can be expensive and they tend to happen when least expected, so if you don’t have an emergency fund then a home warranty can provide relief.
Extra Protection:
A home warranty provides homeowners with reassurance to a home buyer who has limited information about how well the home’s infrastructure has been maintained.
Affordable and Efficient:
A home warranty saves homeowners thousands on upgrading to new appliances when existing ones are malfunctioning or have run their lifetime. With Easy American Home Warranty, you get to benefit from coverage 24/7, 365 days a year.


This is the FAQ page.
Yes, dogs are welcome! Just be sure to keep your dog on a leash at all times and please clean up after him or her.


nslookup
Query name server(s) for various domain records.
More information: home page
- Query your system's default name server for an IP address (A record) of the domain:
nslookup example.com
- Query a given name server for a NS record of the domain:
nslookup -type=NS example.com <IP_ADDRESS>
- Query for a reverse lookup (PTR record) of an IP address:
nslookup -type=PTR <IP_ADDRESS>
- Query for ANY available records using TCP protocol:
nslookup -vc -type=ANY example.com
- Query a given name server for the whole zone file (zone transfer) of the domain using TCP protocol:
nslookup -vc -type=AXFR example.com name_server
- Query for a mail server (MX record) of the domain, showing details of the transaction:
nslookup -type=MX -debug example.com
- Query a given name server on a specific port number for a TXT record of the domain:
nslookup -port=port_number -type=TXT example.com name_server


To use the CommandAPI in your plugins, there are two methods of adding it to your development environment:
Manually using the .jar
- Download the latest CommandAPI.jar from the download page here
- Add the CommandAPI.jar file to your project/environment's build path
- Add the plugin as a dependent in the plugin.yml (
depend: [CommandAPI]
)
Using Maven (recommended)
Developer's Note:
If you've never used maven before, I highly recommend it! It makes it easier to keep your code updated with the latest dependency updates. For information on how to set up a plugin using maven, you can read Bukkit's plugin tutorial.
- Add the maven repository to your
pom.xml
file:
<repositories>
<repository>
<id>mccommandapi</id>
<url>https://raw.githubusercontent.com/JorelAli/1.13-Command-API/mvn-repo/1.13CommandAPI/</url>
</repository>
</repositories>
- Add the dependency to your
pom.xml
:
<dependencies>
<dependency>
<groupId>io.github.jorelali</groupId>
<artifactId>commandapi</artifactId>
<version>VERSION</version>
</dependency>
</dependencies>
A list of version numbers can be found here. For example, if you wanted to use version 2.0, you would use <version>2.0</version>
- Add the plugin as a dependent in the plugin.yml (
depend: [CommandAPI]
)
Using Gradle
- Add the repository to your
build.gradle
file:
repositories {
maven {
name = 'mccommandapi'
url = 'https://raw.githubusercontent.com/JorelAli/1.13-Command-API/mvn-repo/1.13CommandAPI/'
}
}
- Add the dependency to your list of dependencies in your
build.gradle
file:
dependencies {
compile "io.github.jorelali:commandapi:VERSION"
}
A list of version numbers can be found here. For example, if you wanted to use version 2.0, you would use compile "io.github.jorelali:commandapi:2.0"
- Add the plugin as a dependent in the plugin.yml (
depend: [CommandAPI]
)


{% extends "user_site/base.html" %} {% load bootstrap4 %} {% load static %} {% block title %} Help | DCCN {% endblock %} {% block panelTitle %} Help composing message {% endblock %} {% block css %} {% endblock %} {% block body %}
Messaging subsystem allows chairs to compose and send messages to particular users, authors of given submissions or all participants of mailing lists. Each message can be customized in a way that each user receives his/her own copy with specific content.
Message editing is performed in Markdown language. Please note, that most of the Markdown features are not supported right now, and you should use only basic formatting like marking headers, bold and italic font, hyper-links. In particular, tables are yet not supported. However, support for most features will be added in future releases.
Besides markdown formatting, you can use template variables and
template expressions to specify message content for each user or submission.
Template variables represent different properties of a particular user (e.g., first_name
or
user_id
), his/her papers with different status, reviews written by that user. Other variables can target
specific submission, like title
. A set of variables depend on the type of a message you composing.
For instance, submission-specific template variables are available only when composing a message to a set of
submissions.
There are two types of messages:
To put a variable value into the letter, surround the variable name with double curly braces:
{% verbatim %}{{ var }}{% endverbatim %}
. You can also use the variables in
expressions.
Most variables have once of the following types:
String
: most atomic variables are simply strings (e.g., username
or
user_id
). Note, that sometimes variables those look like numbers, should be assumed as strings.
Integer
: variables representing a number of something, e.g. num_papers
.Hyperlink
: variables like conf_email
or conf_site_url
are replaced
with corresponding links. Important: do not put such variables in markdown links!List
: variables like papers_list
are replaced with an unordered list of
items. When these items relate to system objects (like in case of papers_list
), they will provide
hyper-links to these objects.Date
: variables representing date (without time). Most notably, conf_start_date
and conf_end_date
are dates.Datetime
: these variables represent both date and time.Email rendering is based on Django Templates engine, so you can use most of the expressions and filters available there. You can read more about Django Templates here . However, when using these expressions note the following:
.List
variable is evaluated as a String
containing HTML unordered lists with
anchor tags. You should NOT iterate over it..
Hyperlink
type are evaluated as String
containing HTML with an
anchor tag.You can use conditional expressions to display a block of text if the condition is true, and optionally display another block of text otherwise. Conditional expressions take one of two forms:
{% verbatim %}{% if condition %} some text {% endif %}{% endverbatim %}
{% verbatim %}{% if condition %} some text {% else %} another text {% endif %}{% endverbatim %}
Usually you will use conditions like var == 0
and var != 0
to check whether a user
has or has not some types of papers or reviews. Example:
{% verbatim %}
You have {% if num_papers != 0 %}{{ num_papers }}{% else %}no{% endif %} papers.
{% endverbatim %}
This block will output a string "You have 5 papers"
if num_papers = 5
, and
"You have no papers"
otherwise.
Often you need to add some suffix in plural form (most often, -s). You can use pluralization expressions
to do that: {% verbatim %}{{ var|pluralize }}{% endverbatim %}
will print -s
if
var
is not equal to 1
, and nothing otherwise.
If you need another type suffix in plural form, you can specify it right after pluralize
. For
instance, adding -es suffix in plural form looks like this:
{% verbatim %}{{ var|pluralize:"es" }}{% endverbatim %}
Finally, if you need different suffixes in plural and singular form, you can specify both of them separated
with comma (singular first):
{% verbatim %}You have {{ var }} matri{{ var|pluralize:"x,ces" }}{% endverbatim %}
.
You can use date
and time
filters to specify the format in which you want to represent
date or time part of the variable. Read more about format specifiers at
Django documentation.
While you can specify users and submissions to send the message to manually, you can also use mailing lists which contain a list of users or submissions with some property.
To this moment, you can use the following mailing lists:
| ID | Type | Description |
|---|---|---|
| {{ ml.name }} | {{ ml.type }} | {{ ml.details }} |
You can use the following variables in your templates. Please, note that submission variables can be used only in messages sent to submission authors, not in user messages.
{% for var_item in variables %}| Variable | Description |
|---|---|
{{ var.0 }} |
{{ var.1 }} |


--- title: About us description: ---
BLEmap identifies the functionality of Bluetooth Low Energy devices and some of their security issues. BLEmap has been developed with security teams and developers in mind allowing them to either produce human-readable security analsysis reports or computer-readable files that can help automate other parts of the security analisys.
BLEmap can help security teams with no or little experience in Bluetooth to assess the security of Bluetooth-enabled devices. BLEmap executes in minutes, allowing them to expand their services to new kinds of threats and devices with a small cost.
BLEmap has been developed by a team at Royal Holloway with the support from EPSRC and CyberASAP. The funding from EPSRC s part of the Centre for Doctoral Training in Cyber Security at Royal Holloway, University of London (EP/P009301/1).


Sound Board
Drum
Rock
Bob
Metal
Cyall
Jungle
Piano
A1
A2
A3
A4
A5
Animal
Elephant
Wolf
Tiger
Sound Effect
Whisple
Kazoo
Ambulance
Copyright by Project B Team


xxx_is_basic |
Classes | |
| struct | pixel_reference_is_basic |
| Determines if a given pixel reference is basic Basic references must use gil::pixel& (if interleaved), gil::planar_pixel_reference (if planar). They must use the standard constness rules. More... | |
| struct | iterator_is_basic |
| Determines if a given pixel iterator is basic Basic iterators must use gil::pixel (if interleaved), gil::planar_pixel_iterator (if planar) and gil::memory_based_step_iterator (if step). They must use the standard constness rules. More... | |
| struct | locator_is_basic |
| Determines if a given locator is basic. A basic locator is memory-based and has basic x_iterator and y_iterator. More... | |
| struct | view_is_basic |
| Basic views must be over basic locators. More... | |
| struct | image_is_basic |
| Basic images must use basic views and std::allocator of char. More... |


1. Major Pieces
a. Browser makes request to servers using HTTP protocol
i. HTTP – the main protocol of the web
ii. Servers – computers that host the files that make up the web
iii. Internet – the worlds largest computer network
iv. Browser – a program that runs on your computer to display files found on the web
2. HTML – HyperText Markup Language
a. Text content – what you see
b. Markup – what it looks like
c. References to other documents – images and videos
d. Links to other pages
3. HTML Markup
a. Contents
b. Opening tag =
c. Closing tag =
d. All together element
i. bold
ii. italics
iii. Attributes
iv. Anchor -
1. derp
v. Image -
1.
vi. Break -
vii. Paragraph - content
viii. Span - text
ix. Div - text
4. HTML Document
a.
b.
c.
i. Title!
d.
e.
f. content
g.
h.


{{ part.rating }} Registry Star
{{ part.description }}
{{ resultsCount }}
RESULTS
No results found for {{ request.GET.q }}.
Ensure words are spelled correctly.
Try rephrasing keywords or using synonyms.
Try less specific keywords.
Make your queries as concise as possible.
Get additional search tips by visiting Web Search Help.
If you cannot find a page that you know exists, send the address to us.
{{ part.type }}
{{ part.releaseStatus }}
{{ part.sampleStatus }}
{{ part.use }}
{{ part.safety }}
{{ additional.description }}
More...{% include "../login-modal.html" %}


{{Infobox prepared food | name = Shotis puri | image = | caption = Shotis puri | alternate_name = | country = Georgia | region = Europe | creator = | type = Bread | served = | main_ingredient = White flour | variations = | calories = | other = }} Shotis puri or simply Shoti ({{lang-ka|შოთის პური}}) is a traditional Georgian bread made of white flour and shaped like a canoe.<ref>{{cite book | title = The Silk Road Gourmet: Volume One: Western and Southern Asia | author= Laura Kelley |publisher = iUniverse | location= Bloomington, Indiana (USA) | url = http://books.google.com/?id=G6o9n8Kc354C&pg=PA40&dq=shoti#v=onepage&q=shoti&f=false | year = 2009 | pages = 40–41 | isbn = 978-1-4401-4307-6| accessdate = 15 March 2013 }}</ref>
{{portal|Food}} {{Reflist}}
{{commons category|Shotis puri}}
{{Flatbreads}}
{{Georgia-cuisine-stub}} {{bread-stub}}


first task inline css
Hello World
Second task in HW Create a table in index.html
Below table about monitors
third task forms
Enter a phrase
select favorite artist
What is your prefered OS
forth task media


If you don't see the dialog opened, then it might be an issue with this setup (ngDialog + Browserify).
Please submit a new issue to our repository at GitHub.


kicost package¶
Subpackages¶
Submodules¶
kicost.global_vars module¶
Stuff that everybody else needs to know about.
kicost.kicad_config module¶
-
kicost.kicad_config.
bom_plugin_add_entry
(name, cmd, nickname=None, re_flags=2, put_first=True, set_default=True)[source]¶ Add a BOM plugin entry to the Eeschema configuration file.
-
kicost.kicad_config.
bom_plugin_remove_entry
(name, re_flags=2)[source]¶ Remove a BOM plugin entry to the Eeschema configuration file.
kicost.kicost module¶
@package KiCost script, also with Graphical User Interface - GUI, under MIT license for generate part-cost spreadsheets for circuit boards developed with KiCad and others EDAs. Full manual at https://xesscorp.github.io/KiCost Development at https://github.com/xesscorp/KiCost KiCost is powered by the Kitspace PartInfo API (https://kitspace.org/). Partinfo hooks into paid-for 3rd party services. If you find KiCost useful please donate to the Kitspace Open Collective to keep the service running. (https://opencollective.com/kitspace).
- Command line:
kicost -i “%I” “%O.xslx”
- Run Graphical User Interface:
kicost
- Check for help on terminal:
kicost –help
-
kicost.kicost.
kicost
(in_file, eda_name, out_filename, user_fields, ignore_fields, group_fields, translate_fields, variant, dist_list=['newark', 'mouser', 'digikey', 'local_template', 'farnell', 'rs'], collapse_refs=True, supress_cat_url=True, currency='USD')[source]¶ @brief Run KiCost.
Take a schematic input file and create an output file with a cost spreadsheet in xlsx format.
@param in_file list(str()) List of the names of the input BOM files. @param eda_name list(str()) of the EDA modules to be used to open the in_file`list. @param out_filename `str() XLSX output file name. @param user_fields list() of the user fields to be included on the spreadsheet global part. @param ignore_fields list() of the fields to be ignored on the read EDA modules. @param group_fields list() of the fields to be grouped/merged on the function group parts that are not grouped by default. @param translate_fields list() of the fields to translate to translate or remove (if ~ present). @param variant list(str()) of regular expression to the BOM variant of each file in in_file. @param dist_list list(str()) to be scraped, if empty will be scraped with all distributors modules. If None, no web/local distributors will be scraped. @param collapse_refs bool() Collapse or not the designator references in the spreadsheet. Default True. @param supress_cat_url bool() Suppress the distributors catalogue links into the catalogue code in the spreadsheet. Default True. @param currency str() Currency in ISO4217. Default ‘USD’.
-
kicost.kicost.
output_filename
(files_input)[source]¶ @brief Compose a name with the multiple BOM input file names. Compose a name with the multiple BOM input file names, limiting to, at least, the first FILE_OUTPUT_MIN_INPUT characters of each name (avoid huge names by FILE_OUTPUT_MAX_NAME`definition). Join the names of the input files by `FILE_OUTPUT_INPUT_SEP definition. The output folder is the folder of the first file. @param files_input list()`of the input file names. @return `str() file name for the spreadsheet.
kicost.kicost_config module¶
kicost.kicost_gui module¶
kicost.kicost_gui_wxFormBuilder module¶
kicost.kicost_kicadplugin module¶
kicost.os_windows module¶
kicost.sexpdata module¶
S-expression parser for Python¶
sexpdata is a simple S-expression parser/serializer. It has simple load and dump functions like pickle, json or PyYAML module.
>>> from sexpdata import loads, dumps
>>> loads('("a" "b")')
['a', 'b']
>>> print(dumps(['a', 'b']))
("a" "b")
You can install sexpdata from PyPI:
pip install sexpdata
Links:
License¶
sexpdata is licensed under the terms of the BSD 2-Clause License. See the source code for more information.
-
kicost.sexpdata.
load
(filelike, **kwds)[source]¶ Load object from S-expression stored in filelike.
- Parameters
filelike – A text stream object.
See
loads()
for valid keyword arguments.>>> import io >>> fp = io.StringIO() >>> sexp = [Symbol('a'), Symbol('b')] # let's dump and load this object >>> dump(sexp, fp) >>> _ = fp.seek(0) >>> load(fp) == sexp True
-
kicost.sexpdata.
loads
(string, **kwds)[source]¶ Load object from S-expression string.
- Parameters
string – String containing an S-expression.
nil (str or None) – A symbol interpreted as an empty list. Default is
'nil'
.true (str or None) – A symbol interpreted as True. Default is
't'
.false (str or None) – A symbol interpreted as False. Default is
None
.line_comment (str) – Beginning of line comment. Default is
';'
.
>>> loads("(a b)") [Symbol('a'), Symbol('b')] >>> loads("a") Symbol('a') >>> loads("(a 'b)") [Symbol('a'), Quoted(Symbol('b'))] >>> loads("(a '(b))") [Symbol('a'), Quoted([Symbol('b')])] >>> loads(''' ... ;; This is a line comment. ... ("a" "b") ; this is also a comment. ... ''') ['a', 'b'] >>> loads(''' ... # This is a line comment. ... ("a" "b") # this is also a comment. ... ''', line_comment='#') ['a', 'b']
nil
is converted to an empty list by default. You can use keyword argument nil to change what symbol must be interpreted as nil:>>> loads("nil") [] >>> loads("null", nil='null') [] >>> loads("nil", nil=None) Symbol('nil')
t
is converted to True by default. You can use keyword argument true to change what symbol must be converted to True.:>>> loads("t") True >>> loads("#t", true='#t') True >>> loads("t", true=None) Symbol('t')
No symbol is converted to False by default. You can use keyword argument false to convert a symbol to False.
>>> loads("#f") Symbol('#f') >>> loads("#f", false='#f') False >>> loads("nil", false='nil', nil=None) False
-
kicost.sexpdata.
dump
(obj, filelike, **kwds)[source]¶ Write obj as an S-expression into given stream filelike.
- Parameters
obj – A Python object.
filelike – A text stream object.
See
dumps()
for valid keyword arguments.>>> import io >>> fp = io.StringIO() >>> dump([Symbol('a'), Symbol('b')], fp) >>> print(fp.getvalue()) (a b)
-
kicost.sexpdata.
dumps
(obj, **kwds)[source]¶ Convert python object into an S-expression.
- Parameters
obj – A Python object.
str_as (
'symbol'
or'string'
) – How string should be interpreted. Default is'string'
.tuple_as (
'list'
or'array'
) – How tuple should be interpreted. Default is'list'
.true_as (str) – How True should be interpreted. Default is
't'
false_as (str) – How False should be interpreted. Default is
'()'
none_as (str) – How None should be interpreted. Default is
'()'
Basic usage:
>>> print(dumps(['a', 'b'])) ("a" "b") >>> print(dumps(['a', 'b'], str_as='symbol')) (a b) >>> print(dumps(dict(a=1))) (:a 1) >>> print(dumps([None, True, False, ()])) (() t () ()) >>> print(dumps([None, True, False, ()], ... none_as='null', true_as='#t', false_as='#f')) (null #t #f ()) >>> print(dumps(('a', 'b'))) ("a" "b") >>> print(dumps(('a', 'b'), tuple_as='array')) ["a" "b"]
More verbose usage:
>>> print(dumps([Symbol('a'), Symbol('b')])) (a b) >>> print(dumps(Symbol('a'))) a >>> print(dumps([Symbol('a'), Quoted(Symbol('b'))])) (a 'b) >>> print(dumps([Symbol('a'), Quoted([Symbol('b')])])) (a '(b))
-
kicost.sexpdata.
car
(obj)[source]¶ Alias of
obj[0]
.>>> car(loads('(a . b)')) Symbol('a') >>> car(loads('(a b)')) Symbol('a')
-
kicost.sexpdata.
cdr
(obj)[source]¶ cdr-like function.
>>> cdr(loads('(a . b)')) Symbol('b') >>> cdr(loads('(a b)')) [Symbol('b')] >>> cdr(loads('(a . (b))')) [Symbol('b')] >>> cdr(loads('(a)')) [] >>> cdr(loads('(a . nil)')) []
kicost.spreadsheet module¶
kicost.version module¶
kicost.wxAnyThread module¶
In wxPython, methods that alter the state of the GUI are only safe to call from the thread running the main event loop. Other threads must typically post events to the GUI thread instead of invoking methods directly.
While there are builtin shortcuts for this (e.g. wx.CallAfter) they do not capture the full semantics of a function call. This module provides an easy way to invoke methods from any thread transparently, propagating return values and exceptions back to the calling thread.
The main interface is a decorator named “anythread”, which can be applied to methods to make them safe to call from any thread, like so:
from .wxAnyThread import anythread # For correct use of the threads with the GUI in wxPython.
class MyFrame(wx.Frame):
@anythread def GetSomeData():
dlg = MyQueryDialog(self,”Enter some data”) if dlg.ShowModal() == wx.ID_OK:
resp = dlg.GetResponse() return int(resp)
- else:
raise NoDataEnteredError()
The GetSomeData method can now be directly invoked from any thread. The calling thread will block while the main GUI thread shows the dialog, and will then receive a return value or exception as appropriate.
-
kicost.wxAnyThread.
anythread
(func)[source]¶ Method decorator allowing call from any thread.
The method is replaced by one that posts a MethodInvocationEvent to the object, then blocks waiting for it to be completed. The target object is automatically connected to the _EVT_INVOKE_METHOD event if it wasn’t alread connected.
When invoked from the main thread, the function is executed immediately.


Position: Founder & Director
About us: Youth organization that seeks to generate impact in society through altruistic, ecological and animal rescue activities.
Mision: To expand our work to achieve a greater reach and thus help more people in need.
Vision: To guide and encourage young people to care about their social environment and practice charity events.
Position: Former Civic & Social Engagement Officer and Chair
SHPE'S Mision: SHPE changes lives by empowering the Hispanic community to realize its fullest potential and to impact the world through STEM awareness, access, support, and development.
SHEP'S Vision: SHPE’s vision is a world where Hispanics are highly valued and influential as the leading innovators, scientists, mathematicians, and engineers.
MAES' Mision: To promote, cultivate, and honor excellence in education and leadership among Latino engineers and scientists.
MAES' Vision: MAES is the foremost Latino organization for the development of STEM leaders in the academic, executive, and technical communities


When the user selects an item from a list, we want to store that selection so we can react to it. Create an observable object to hold the selected child.
public class PhoneBookSelection { public virtual Person SelectedPerson { get; set; } }
private void MainPage_Loaded(object sender, RoutedEventArgs e) { // ... PhoneBookSelection selection = KO.NewObservable<PhoneBookSelection>(); // ... }
Define a computed property to return the projection of the selected child. A computed property can also have an inverse, to set the selected child when the projection is selected.
private void MainPage_Loaded(object sender, RoutedEventArgs e) { // ... DataContext = KO.ApplyBindings(phoneBook, new { // ... SelectedPerson = KO.Computed( () => PersonSummary.FromPerson(selection.SelectedPerson), value => selection.SelectedPerson = PersonSummary.ToPerson(value) ) }); }
Where FromPerson and ToPerson are a couple of helper methods that handle nulls.
public static PersonSummary FromPerson(Person person) { return person == null ? null : new PersonSummary(person); } public static Person ToPerson(PersonSummary personSummary) { return personSummary == null ? null : personSummary.Person; }
Commands can have conditions. The button is only enabled when the condition is true.
private void MainPage_Loaded(object sender, RoutedEventArgs e) { // ... DataContext = KO.ApplyBindings(phoneBook, new { // ... DeletePerson = KO.Command(() => { phoneBook.People.Remove(selection.SelectedPerson); selection.SelectedPerson = null; }, () => selection.SelectedPerson != null ) }); }
Define another computed property to return the actual child, not its projection. This will allow the user to set properties on the child itself.
private void MainPage_Loaded(object sender, RoutedEventArgs e) { // ... DataContext = KO.ApplyBindings(phoneBook, new { // ... PersonDetail = KO.Computed(() => selection.SelectedPerson) }); }
Data bind the collection to the ItemsSource property, and the selected projection to the SelectedItem property. Data bind properties of the selected child so that the user can edit them.
<ListBox ItemsSource="{Binding People}" SelectedItem="{Binding SelectedPerson, Mode=TwoWay}"> <ListBox.ItemTemplate> <DataTemplate> <TextBlock Text="{Binding Name}"/> </DataTemplate> </ListBox.ItemTemplate> </ListBox> <TextBox Text="{Binding PersonDetail.FirstName, Mode=TwoWay}"/> <TextBox Text="{Binding PersonDetail.LastName, Mode=TwoWay}"/>


Secret Paragraph
Number of times the button has been clicked: {{count}}
4 ? 'blue' : 'transparent'}" [ngClass]="{'color' : x > 4}">Hello World


The graphical interface of this service is not configured correctly. Please contact the site administrators.


symbIoTe
Resources
Resources Found
Sensor
Longitude
Latitude
Altitude
Platform
Observed Properties
Owner
Location
Search
Platform name:
Name:
Owner:
Observed property:
Location name:
Location position:
Pick location on map
Reset location
Date
Time
Measurement
Observed Property
Unit
Location name
Latitude
Longitude
Something went wrong...
It was not possible to get sensor historical data. Please try again.
×
Map Legend
Map Legend goes here...


FIND(1) FIND(1) NAME find - search for files in a directory hierarchy SYNOPSIS find [-H] [-L] [-P] [-D debugopts] [-Olevel] [path...] [expression] DESCRIPTION This manual page documents the GNU version of find. GNU find searches the directory tree rooted at each given file name by evaluating the given expression from left to right, according to the rules of precedence (see section OPERATORS), until the outcome is known (the left hand side is false for and operations, true for or), at which point find moves on to the next file name. If you are using find in an environment where security is important (for example if you are using it to search directories that are writable by other users), you should read the "Security Considerations" chapter of the findutils documentation, which is called Finding Files and comes with findutils. That document also includes a lot more detail and discussion than this manual page, so you may find it a more useful source of infor‐ mation. OPTIONS The -H, -L and -P options control the treatment of symbolic links. Com‐ mand-line arguments following these are taken to be names of files or directories to be examined, up to the first argument that begins with `-', or the argument `(' or `!'. That argument and any following argu‐ ments are taken to be the expression describing what is to be searched for. If no paths are given, the current directory is used. If no expression is given, the expression -print is used (but you should proba‐ bly consider using -print0 instead, anyway). This manual page talks about `options' within the expression list. These options control the behaviour of find but are specified immediately after the last path name. The five `real' options -H, -L, -P, -D and -O must appear before the first path name, if at all. A double dash -- can also be used to signal that any remaining arguments are not options (though ensuring that all start points begin with either `./' or `/' is generally safer if you use wildcards in the list of start points). -P Never follow symbolic links. This is the default behaviour. When find examines or prints information a file, and the file is a sym‐ bolic link, the information used shall be taken from the proper‐ ties of the symbolic link itself. -L Follow symbolic links. When find examines or prints information about files, the information used shall be taken from the proper‐ ties of the file to which the link points, not from the link itself (unless it is a broken symbolic link or find is unable to examine the file to which the link points). Use of this option implies -noleaf. If you later use the -P option, -noleaf will still be in effect. If -L is in effect and find discovers a sym‐ bolic link to a subdirectory during its search, the subdirectory pointed to by the symbolic link will be searched. When the -L option is in effect, the -type predicate will always match against the type of the file that a symbolic link points to rather than the link itself (unless the symbolic link is broken). Using -L causes the -lname and -ilname predicates always to return false. -H Do not follow symbolic links, except while processing the command line arguments. When find examines or prints information about files, the information used shall be taken from the properties of the symbolic link itself. The only exception to this behaviour is when a file specified on the command line is a symbolic link, and the link can be resolved. For that situation, the information used is taken from whatever the link points to (that is, the link is followed). The information about the link itself is used as a fallback if the file pointed to by the symbolic link cannot be examined. If -H is in effect and one of the paths specified on the command line is a symbolic link to a directory, the contents of that directory will be examined (though of course -maxdepth 0 would prevent this). If more than one of -H, -L and -P is specified, each overrides the oth‐ ers; the last one appearing on the command line takes effect. Since it is the default, the -P option should be considered to be in effect unless either -H or -L is specified. GNU find frequently stats files during the processing of the command line itself, before any searching has begun. These options also affect how those arguments are processed. Specifically, there are a number of tests that compare files listed on the command line against a file we are cur‐ rently considering. In each case, the file specified on the command line will have been examined and some of its properties will have been saved. If the named file is in fact a symbolic link, and the -P option is in effect (or if neither -H nor -L were specified), the information used for the comparison will be taken from the properties of the symbolic link. Otherwise, it will be taken from the properties of the file the link points to. If find cannot follow the link (for example because it has insufficient privileges or the link points to a nonexistent file) the properties of the link itself will be used. When the -H or -L options are in effect, any symbolic links listed as the argument of -newer will be dereferenced, and the timestamp will be taken from the file to which the symbolic link points. The same consideration applies to -newerXY, -anewer and -cnewer. The -follow option has a similar effect to -L, though it takes effect at the point where it appears (that is, if -L is not used but -follow is, any symbolic links appearing after -follow on the command line will be dereferenced, and those before it will not). -D debugoptions Print diagnostic information; this can be helpful to diagnose problems with why find is not doing what you want. The list of debug options should be comma separated. Compatibility of the debug options is not guaranteed between releases of findutils. For a complete list of valid debug options, see the output of find -D help. Valid debug options include help Explain the debugging options tree Show the expression tree in its original and optimised form. stat Print messages as files are examined with the stat and lstat system calls. The find program tries to minimise such calls. opt Prints diagnostic information relating to the optimisation of the expression tree; see the -O option. rates Prints a summary indicating how often each predicate suc‐ ceeded or failed. -Olevel Enables query optimisation. The find program reorders tests to speed up execution while preserving the overall effect; that is, predicates with side effects are not reordered relative to each other. The optimisations performed at each optimisation level are as follows. 0 Equivalent to optimisation level 1. 1 This is the default optimisation level and corresponds to the traditional behaviour. Expressions are reordered so that tests based only on the names of files (for example -name and -regex) are performed first. 2 Any -type or -xtype tests are performed after any tests based only on the names of files, but before any tests that require information from the inode. On many modern ver‐ sions of Unix, file types are returned by readdir() and so these predicates are faster to evaluate than predicates which need to stat the file first. 3 At this optimisation level, the full cost-based query opti‐ miser is enabled. The order of tests is modified so that cheap (i.e. fast) tests are performed first and more expen‐ sive ones are performed later, if necessary. Within each cost band, predicates are evaluated earlier or later according to whether they are likely to succeed or not. For -o, predicates which are likely to succeed are evalu‐ ated earlier, and for -a, predicates which are likely to fail are evaluated earlier. The cost-based optimiser has a fixed idea of how likely any given test is to succeed. In some cases the probability takes account of the specific nature of the test (for example, -type f is assumed to be more likely to succeed than -type c). The cost- based optimiser is currently being evaluated. If it does not actually improve the performance of find, it will be removed again. Conversely, optimisations that prove to be reliable, robust and effective may be enabled at lower optimisation levels over time. However, the default behaviour (i.e. optimisation level 1) will not be changed in the 4.3.x release series. The findutils test suite runs all the tests on find at each optimisa‐ tion level and ensures that the result is the same. EXPRESSIONS The expression is made up of options (which affect overall operation rather than the processing of a specific file, and always return true), tests (which return a true or false value), and actions (which have side effects and return a true or false value), all separated by operators. -and is assumed where the operator is omitted. If the expression contains no actions other than -prune, -print is per‐ formed on all files for which the expression is true. OPTIONS All options always return true. Except for -daystart, -follow and -regextype, the options affect all tests, including tests specified before the option. This is because the options are processed when the command line is parsed, while the tests don't do anything until files are examined. The -daystart, -follow and -regextype options are different in this respect, and have an effect only on tests which appear later in the command line. Therefore, for clarity, it is best to place them at the beginning of the expression. A warning is issued if you don't do this. -d A synonym for -depth, for compatibility with FreeBSD, NetBSD, Mac‐ OS X and OpenBSD. -daystart Measure times (for -amin, -atime, -cmin, -ctime, -mmin, and -mtime) from the beginning of today rather than from 24 hours ago. This option only affects tests which appear later on the command line. -depth Process each directory's contents before the directory itself. The -delete action also implies -depth. -follow Deprecated; use the -L option instead. Dereference symbolic links. Implies -noleaf. The -follow option affects only those tests which appear after it on the command line. Unless the -H or -L option has been specified, the position of the -follow option changes the behaviour of the -newer predicate; any files listed as the argument of -newer will be dereferenced if they are symbolic links. The same consideration applies to -newerXY, -anewer and -cnewer. Similarly, the -type predicate will always match against the type of the file that a symbolic link points to rather than the link itself. Using -follow causes the -lname and -ilname predicates always to return false. -help, --help Print a summary of the command-line usage of find and exit. -ignore_readdir_race Normally, find will emit an error message when it fails to stat a file. If you give this option and a file is deleted between the time find reads the name of the file from the directory and the time it tries to stat the file, no error message will be issued. This also applies to files or directories whose names are given on the command line. This option takes effect at the time the com‐ mand line is read, which means that you cannot search one part of the filesystem with this option on and part of it with this option off (if you need to do that, you will need to issue two find com‐ mands instead, one with the option and one without it). -maxdepth levels Descend at most levels (a non-negative integer) levels of directo‐ ries below the command line arguments. -maxdepth 0 means only apply the tests and actions to the command line argu‐ ments. -mindepth levels Do not apply any tests or actions at levels less than levels (a non-negative integer). -mindepth 1 means process all files except the command line arguments. -mount Don't descend directories on other filesystems. An alternate name for -xdev, for compatibility with some other versions of find. -noignore_readdir_race Turns off the effect of -ignore_readdir_race. -noleaf Do not optimize by assuming that directories contain 2 fewer sub‐ directories than their hard link count. This option is needed when searching filesystems that do not follow the Unix directory- link convention, such as CD-ROM or MS-DOS filesystems or AFS vol‐ ume mount points. Each directory on a normal Unix filesystem has at least 2 hard links: its name and its `.' entry. Additionally, its subdirectories (if any) each have a `..' entry linked to that directory. When find is examining a directory, after it has stat‐ ted 2 fewer subdirectories than the directory's link count, it knows that the rest of the entries in the directory are non-direc‐ tories (`leaf' files in the directory tree). If only the files' names need to be examined, there is no need to stat them; this gives a significant increase in search speed. -regextype type Changes the regular expression syntax understood by -regex and -iregex tests which occur later on the command line. Currently- implemented types are emacs (this is the default), posix-awk, posix-basic, posix-egrep and posix-extended. -version, --version Print the find version number and exit. -warn, -nowarn Turn warning messages on or off. These warnings apply only to the command line usage, not to any conditions that find might encounter when it searches directories. The default behaviour corresponds to -warn if standard input is a tty, and to -nowarn otherwise. -xdev Don't descend directories on other filesystems. TESTS Some tests, for example -newerXY and -samefile, allow comparison between the file currently being examined and some reference file specified on the command line. When these tests are used, the interpretation of the reference file is determined by the options -H, -L and -P and any previ‐ ous -follow, but the reference file is only examined once, at the time the command line is parsed. If the reference file cannot be examined (for example, the stat(2) system call fails for it), an error message is issued, and find exits with a nonzero status. Numeric arguments can be specified as +n for greater than n, -n for less than n, n for exactly n. -amin n File was last accessed n minutes ago. -anewer file File was last accessed more recently than file was modified. If file is a symbolic link and the -H option or the -L option is in effect, the access time of the file it points to is always used. -atime n File was last accessed n*24 hours ago. When find figures out how many 24-hour periods ago the file was last accessed, any frac‐ tional part is ignored, so to match -atime +1, a file has to have been accessed at least two days ago. -cmin n File's status was last changed n minutes ago. -cnewer file File's status was last changed more recently than file was modi‐ fied. If file is a symbolic link and the -H option or the -L option is in effect, the status-change time of the file it points to is always used. -ctime n File's status was last changed n*24 hours ago. See the comments for -atime to understand how rounding affects the interpretation of file status change times. -empty File is empty and is either a regular file or a directory. -executable Matches files which are executable and directories which are searchable (in a file name resolution sense). This takes into account access control lists and other permissions artefacts which the -perm test ignores. This test makes use of the access(2) sys‐ tem call, and so can be fooled by NFS servers which do UID mapping (or root-squashing), since many systems implement access(2) in the client's kernel and so cannot make use of the UID mapping informa‐ tion held on the server. Because this test is based only on the result of the access(2) system call, there is no guarantee that a file for which this test succeeds can actually be executed. -false Always false. -fstype type File is on a filesystem of type type. The valid filesystem types vary among different versions of Unix; an incomplete list of filesystem types that are accepted on some version of Unix or another is: ufs, 4.2, 4.3, nfs, tmp, mfs, S51K, S52K. You can use -printf with the %F directive to see the types of your filesys‐ tems. -gid n File's numeric group ID is n. -group gname File belongs to group gname (numeric group ID allowed). -ilname pattern Like -lname, but the match is case insensitive. If the -L option or the -follow option is in effect, this test returns false unless the symbolic link is broken. -iname pattern Like -name, but the match is case insensitive. For example, the patterns `fo*' and `F??' match the file names `Foo', `FOO', `foo', `fOo', etc. In these patterns, unlike filename expansion by the shell, an initial '.' can be matched by `*'. That is, find -name *bar will match the file `.foobar'. Please note that you should quote patterns as a matter of course, otherwise the shell will expand any wildcard characters in them. -inum n File has inode number n. It is normally easier to use the -same‐ file test instead. -ipath pattern Behaves in the same way as -iwholename. This option is depre‐ cated, so please do not use it. -iregex pattern Like -regex, but the match is case insensitive. -iwholename pattern Like -wholename, but the match is case insensitive. -links n File has n links. -lname pattern File is a symbolic link whose contents match shell pattern pat‐ tern. The metacharacters do not treat `/' or `.' specially. If the -L option or the -follow option is in effect, this test returns false unless the symbolic link is broken. -mmin n File's data was last modified n minutes ago. -mtime n File's data was last modified n*24 hours ago. See the comments for -atime to understand how rounding affects the interpretation of file modification times. -name pattern Base of file name (the path with the leading directories removed) matches shell pattern pattern. The metacharacters (`*', `?', and `[]') match a `.' at the start of the base name (this is a change in findutils-4.2.2; see section STANDARDS CONFORMANCE below). To ignore a directory and the files under it, use -prune; see an example in the description of -path. Braces are not recognised as being special, despite the fact that some shells including Bash imbue braces with a special meaning in shell patterns. The file‐ name matching is performed with the use of the fnmatch(3) library function. Don't forget to enclose the pattern in quotes in order to protect it from expansion by the shell. -newer file File was modified more recently than file. If file is a symbolic link and the -H option or the -L option is in effect, the modifi‐ cation time of the file it points to is always used. -newerXY reference Compares the timestamp of the current file with reference. The reference argument is normally the name of a file (and one of its timestamps is used for the comparison) but it may also be a string describing an absolute time. X and Y are placeholders for other letters, and these letters select which time belonging to how ref‐ erence is used for the comparison. ll ll ll ll llw(2i). a The access time of the file reference B The birth time of the file reference c The inode status change time of reference m The modification time of the file reference t reference is interpreted directly as a time Some combinations are invalid; for example, it is invalid for X to be t. Some combinations are not implemented on all systems; for example B is not supported on all systems. If an invalid or unsupported combination of XY is specified, a fatal error results. Time specifications are interpreted as for the argument to the -d option of GNU date. If you try to use the birth time of a refer‐ ence file, and the birth time cannot be determined, a fatal error message results. If you specify a test which refers to the birth time of files being examined, this test will fail for any files where the birth time is unknown. -nogroup No group corresponds to file's numeric group ID. -nouser No user corresponds to file's numeric user ID. -path pattern File name matches shell pattern pattern. The metacharacters do not treat `/' or `.' specially; so, for example, find . -path "./sr*sc" will print an entry for a directory called `./src/misc' (if one exists). To ignore a whole directory tree, use -prune rather than checking every file in the tree. For example, to skip the direc‐ tory `src/emacs' and all files and directories under it, and print the names of the other files found, do something like this: find . -path ./src/emacs -prune -o -print Note that the pattern match test applies to the whole file name, starting from one of the start points named on the command line. It would only make sense to use an absolute path name here if the relevant start point is also an absolute path. This means that this command will never match anything: find bar -path /foo/bar/myfile -print The predicate -path is also supported by HP-UX find and will be in a forthcoming version of the POSIX standard. -perm mode File's permission bits are exactly mode (octal or symbolic). Since an exact match is required, if you want to use this form for symbolic modes, you may have to specify a rather complex mode string. For example -perm g=w will only match files which have mode 0020 (that is, ones for which group write permission is the only permission set). It is more likely that you will want to use the `/' or `-' forms, for example -perm -g=w, which matches any file with group write permission. See the EXAMPLES section for some illustrative examples. -perm -mode All of the permission bits mode are set for the file. Symbolic modes are accepted in this form, and this is usually the way in which would want to use them. You must specify `u', `g' or `o' if you use a symbolic mode. See the EXAMPLES section for some illustrative examples. -perm /mode Any of the permission bits mode are set for the file. Symbolic modes are accepted in this form. You must specify `u', `g' or `o' if you use a symbolic mode. See the EXAMPLES section for some illustrative examples. If no permission bits in mode are set, this test matches any file (the idea here is to be consistent with the behaviour of -perm -000). -perm +mode Deprecated, old way of searching for files with any of the permis‐ sion bits in mode set. You should use -perm /mode instead. Trying to use the `+' syntax with symbolic modes will yield surprising results. For example, `+u+x' is a valid symbolic mode (equivalent to +u,+x, i.e. 0111) and will therefore not be evaluated as -perm +mode but instead as the exact mode specifier -perm mode and so it matches files with exact permissions 0111 instead of files with any execute bit set. If you found this paragraph confusing, you're not alone - just use -perm /mode. This form of the -perm test is deprecated because the POSIX specification requires the interpretation of a leading `+' as being part of a symbolic mode, and so we switched to using `/' instead. -readable Matches files which are readable. This takes into account access control lists and other permissions artefacts which the -perm test ignores. This test makes use of the access(2) system call, and so can be fooled by NFS servers which do UID mapping (or root-squash‐ ing), since many systems implement access(2) in the client's ker‐ nel and so cannot make use of the UID mapping information held on the server. -regex pattern File name matches regular expression pattern. This is a match on the whole path, not a search. For example, to match a file named `./fubar3', you can use the regular expression `.*bar.' or `.*b.*3', but not `f.*r3'. The regular expressions understood by find are by default Emacs Regular Expressions, but this can be changed with the -regextype option. -samefile name File refers to the same inode as name. When -L is in effect, this can include symbolic links. -size n[cwbkMG] File uses n units of space. The following suffixes can be used: `b' for 512-byte blocks (this is the default if no suffix is used) `c' for bytes `w' for two-byte words `k' for Kilobytes (units of 1024 bytes) `M' for Megabytes (units of 1048576 bytes) `G' for Gigabytes (units of<PHONE_NUMBER> bytes) The size does not count indirect blocks, but it does count blocks in sparse files that are not actually allocated. Bear in mind that the `%k' and `%b' format specifiers of -printf handle sparse files differently. The `b' suffix always denotes 512-byte blocks and never 1 Kilobyte blocks, which is different to the behaviour of -ls. -true Always true. -type c File is of type c: b block (buffered) special c character (unbuffered) special d directory p named pipe (FIFO) f regular file l symbolic link; this is never true if the -L option or the -follow option is in effect, unless the symbolic link is broken. If you want to search for symbolic links when -L is in effect, use -xtype. s socket D door (Solaris) -uid n File's numeric user ID is n. -used n File was last accessed n days after its status was last changed. -user uname File is owned by user uname (numeric user ID allowed). -wholename pattern See -path. This alternative is less portable than -path. -writable Matches files which are writable. This takes into account access control lists and other permissions artefacts which the -perm test ignores. This test makes use of the access(2) system call, and so can be fooled by NFS servers which do UID mapping (or root-squash‐ ing), since many systems implement access(2) in the client's ker‐ nel and so cannot make use of the UID mapping information held on the server. -xtype c The same as -type unless the file is a symbolic link. For sym‐ bolic links: if the -H or -P option was specified, true if the file is a link to a file of type c; if the -L option has been given, true if c is `l'. In other words, for symbolic links, -xtype checks the type of the file that -type does not check. ACTIONS -delete Delete files; true if removal succeeded. If the removal failed, an error message is issued. If -delete fails, find's exit status will be nonzero (when it eventually exits). Use of -delete auto‐ matically turns on the -depth option. Warnings: Don't forget that the find command line is evaluated as an expression, so putting -delete first will make find try to delete everything below the starting points you specified. When testing a find command line that you later intend to use with -delete, you should explicitly specify -depth in order to avoid later surprises. Because -delete implies -depth, you cannot use‐ fully use -prune and -delete together. -exec command ; Execute command; true if 0 status is returned. All following arguments to find are taken to be arguments to the command until an argument consisting of `;' is encountered. The string `{}' is replaced by the current file name being processed everywhere it occurs in the arguments to the command, not just in arguments where it is alone, as in some versions of find. Both of these constructions might need to be escaped (with a `\') or quoted to protect them from expansion by the shell. See the EXAMPLES sec‐ tion for examples of the use of the -exec option. The specified command is run once for each matched file. The command is exe‐ cuted in the starting directory. There are unavoidable security problems surrounding use of the -exec action; you should use the -execdir option instead. -exec command {} + This variant of the -exec action runs the specified command on the selected files, but the command line is built by appending each selected file name at the end; the total number of invocations of the command will be much less than the number of matched files. The command line is built in much the same way that xargs builds its command lines. Only one instance of `{}' is allowed within the command. The command is executed in the starting directory. -execdir command ; -execdir command {} + Like -exec, but the specified command is run from the subdirectory containing the matched file, which is not normally the directory in which you started find. This a much more secure method for invoking commands, as it avoids race conditions during resolution of the paths to the matched files. As with the -exec action, the `+' form of -execdir will build a command line to process more than one matched file, but any given invocation of command will only list files that exist in the same subdirectory. If you use this option, you must ensure that your $PATH environment variable does not reference `.'; otherwise, an attacker can run any com‐ mands they like by leaving an appropriately-named file in a direc‐ tory in which you will run -execdir. The same applies to having entries in $PATH which are empty or which are not absolute direc‐ tory names. -fls file True; like -ls but write to file like -fprint. The output file is always created, even if the predicate is never matched. See the UNUSUAL FILENAMES section for information about how unusual char‐ acters in filenames are handled. -fprint file True; print the full file name into file file. If file does not exist when find is run, it is created; if it does exist, it is truncated. The file names ``/dev/stdout'' and ``/dev/stderr'' are handled specially; they refer to the standard output and standard error output, respectively. The output file is always created, even if the predicate is never matched. See the UNUSUAL FILENAMES section for information about how unusual characters in filenames are handled. -fprint0 file True; like -print0 but write to file like -fprint. The output file is always created, even if the predicate is never matched. See the UNUSUAL FILENAMES section for information about how unusual characters in filenames are handled. -fprintf file format True; like -printf but write to file like -fprint. The output file is always created, even if the predicate is never matched. See the UNUSUAL FILENAMES section for information about how unusual characters in filenames are handled. -ls True; list current file in ls -dils format on standard output. The block counts are of 1K blocks, unless the environment variable POSIXLY_CORRECT is set, in which case 512-byte blocks are used. See the UNUSUAL FILENAMES section for information about how unusual characters in filenames are handled. -ok command ; Like -exec but ask the user first. If the user agrees, run the command. Otherwise just return false. If the command is run, its standard input is redirected from /dev/null. The response to the prompt is matched against a pair of regular expressions to determine if it is an affirmative or negative response. This regular expression is obtained from the system if the `POSIXLY_CORRECT' environment variable is set, or otherwise from find's message translations. If the system has no suitable definition, find's own definition will be used. In either case, the interpretation of the regular expression itself will be affected by the environment variables 'LC_CTYPE' (character classes) and 'LC_COLLATE' (character ranges and equivalence classes). -okdir command ; Like -execdir but ask the user first in the same way as for -ok. If the user does not agree, just return false. If the command is run, its standard input is redirected from /dev/null. -print True; print the full file name on the standard output, followed by a newline. If you are piping the output of find into another program and there is the faintest possibility that the files which you are searching for might contain a newline, then you should seriously consider using the -print0 option instead of -print. See the UNUSUAL FILENAMES section for information about how unusual characters in filenames are handled. -print0 True; print the full file name on the standard output, followed by a null character (instead of the newline character that -print uses). This allows file names that contain newlines or other types of white space to be correctly interpreted by programs that process the find output. This option corresponds to the -0 option of xargs. -printf format True; print format on the standard output, interpreting `\' escapes and `%' directives. Field widths and precisions can be specified as with the `printf' C function. Please note that many of the fields are printed as %s rather than %d, and this may mean that flags don't work as you might expect. This also means that the `-' flag does work (it forces fields to be left-aligned). Unlike -print, -printf does not add a newline at the end of the string. The escapes and directives are: \a Alarm bell. \b Backspace. \c Stop printing from this format immediately and flush the output. \f Form feed. \n Newline. \r Carriage return. \t Horizontal tab. \v Vertical tab. \0 ASCII NUL. \\ A literal backslash (`\'). \NNN The character whose ASCII code is NNN (octal). A `\' character followed by any other character is treated as an ordinary character, so they both are printed. %% A literal percent sign. %a File's last access time in the format returned by the C `ctime' function. %Ak File's last access time in the format specified by k, which is either `@' or a directive for the C `strftime' function. The possible values for k are listed below; some of them might not be available on all systems, due to differences in `strftime' between systems. @ seconds since Jan. 1, 1970, 00:00 GMT, with frac‐ tional part. Time fields: H hour (00..23) I hour (01..12) k hour ( 0..23) l hour ( 1..12) M minute (00..59) p locale's AM or PM r time, 12-hour (hh:mm:ss [AP]M) S Second (00.00 .. 61.00). There is a fractional part. T time, 24-hour (hh:mm:ss) + Date and time, separated by `+', for example `2004-04-28+22:22:05.0'. This is a GNU extension. The time is given in the current timezone (which may be affected by setting the TZ environment variable). The seconds field includes a fractional part. X locale's time representation (H:M:S) Z time zone (e.g., EDT), or nothing if no time zone is determinable Date fields: a locale's abbreviated weekday name (Sun..Sat) A locale's full weekday name, variable length (Sun‐ day..Saturday) b locale's abbreviated month name (Jan..Dec) B locale's full month name, variable length (Janu‐ ary..December) c locale's date and time (Sat Nov 04 12:02:33 EST 1989). The format is the same as for ctime(3) and so to preserve compatibility with that format, there is no fractional part in the seconds field. d day of month (01..31) D date (mm/dd/yy) h same as b j day of year (001..366) m month (01..12) U week number of year with Sunday as first day of week (00..53) w day of week (0..6) W week number of year with Monday as first day of week (00..53) x locale's date representation (mm/dd/yy) y last two digits of year (00..99) Y year (1970...) %b The amount of disk space used for this file in 512-byte blocks. Since disk space is allocated in multiples of the filesystem block size this is usually greater than %s/512, but it can also be smaller if the file is a sparse file. %c File's last status change time in the format returned by the C `ctime' function. %Ck File's last status change time in the format specified by k, which is the same as for %A. %d File's depth in the directory tree; 0 means the file is a command line argument. %D The device number on which the file exists (the st_dev field of struct stat), in decimal. %f File's name with any leading directories removed (only the last element). %F Type of the filesystem the file is on; this value can be used for -fstype. %g File's group name, or numeric group ID if the group has no name. %G File's numeric group ID. %h Leading directories of file's name (all but the last ele‐ ment). If the file name contains no slashes (since it is in the current directory) the %h specifier expands to ".". %H Command line argument under which file was found. %i File's inode number (in decimal). %k The amount of disk space used for this file in 1K blocks. Since disk space is allocated in multiples of the filesys‐ tem block size this is usually greater than %s/1024, but it can also be smaller if the file is a sparse file. %l Object of symbolic link (empty string if file is not a sym‐ bolic link). %m File's permission bits (in octal). This option uses the `traditional' numbers which most Unix implementations use, but if your particular implementation uses an unusual ordering of octal permissions bits, you will see a differ‐ ence between the actual value of the file's mode and the output of %m. Normally you will want to have a leading zero on this number, and to do this, you should use the # flag (as in, for example, `%#m'). %M File's permissions (in symbolic form, as for ls). This directive is supported in findutils 4.2.5 and later. %n Number of hard links to file. %p File's name. %P File's name with the name of the command line argument under which it was found removed. %s File's size in bytes. %S File's sparseness. This is calculated as (BLOCK‐ SIZE*st_blocks / st_size). The exact value you will get for an ordinary file of a certain length is system-depen‐ dent. However, normally sparse files will have values less than 1.0, and files which use indirect blocks may have a value which is greater than 1.0. The value used for BLOCKSIZE is system-dependent, but is usually 512 bytes. If the file size is zero, the value printed is undefined. On systems which lack support for st_blocks, a file's sparseness is assumed to be 1.0. %t File's last modification time in the format returned by the C `ctime' function. %Tk File's last modification time in the format specified by k, which is the same as for %A. %u File's user name, or numeric user ID if the user has no name. %U File's numeric user ID. %y File's type (like in ls -l), U=unknown type (shouldn't hap‐ pen) %Y File's type (like %y), plus follow symlinks: L=loop, N=nonexistent A `%' character followed by any other character is discarded, but the other character is printed (don't rely on this, as further format characters may be introduced). A `%' at the end of the format argument causes undefined behaviour since there is no fol‐ lowing character. In some locales, it may hide your door keys, while in others it may remove the final page from the novel you are reading. The %m and %d directives support the # , 0 and + flags, but the other directives do not, even if they print numbers. Numeric directives that do not support these flags include G, U, b, D, k and n. The `-' format flag is supported and changes the alignment of a field from right-justified (which is the default) to left- justified. See the UNUSUAL FILENAMES section for information about how unusual characters in filenames are handled. -prune True; if the file is a directory, do not descend into it. If -depth is given, false; no effect. Because -delete implies -depth, you cannot usefully use -prune and -delete together. -quit Exit immediately. No child processes will be left running, but no more paths specified on the command line will be processed. For example, find /tmp/foo /tmp/bar -print -quit will print only /tmp/foo. Any command lines which have been built up with -execdir ... {} + will be invoked before find exits. The exit status may or may not be zero, depending on whether an error has already occurred. UNUSUAL FILENAMES Many of the actions of find result in the printing of data which is under the control of other users. This includes file names, sizes, modifica‐ tion times and so forth. File names are a potential problem since they can contain any character except `\0' and `/'. Unusual characters in file names can do unexpected and often undesirable things to your termi‐ nal (for example, changing the settings of your function keys on some terminals). Unusual characters are handled differently by various actions, as described below. -print0, -fprint0 Always print the exact filename, unchanged, even if the output is going to a terminal. -ls, -fls Unusual characters are always escaped. White space, backslash, and double quote characters are printed using C-style escaping (for example `\f', `\"'). Other unusual characters are printed using an octal escape. Other printable characters (for -ls and -fls these are the characters between octal 041 and 0176) are printed as-is. -printf, -fprintf If the output is not going to a terminal, it is printed as-is. Otherwise, the result depends on which directive is in use. The directives %D, %F, %g, %G, %H, %Y, and %y expand to values which are not under control of files' owners, and so are printed as-is. The directives %a, %b, %c, %d, %i, %k, %m, %M, %n, %s, %t, %u and %U have values which are under the control of files' owners but which cannot be used to send arbitrary data to the terminal, and so these are printed as-is. The directives %f, %h, %l, %p and %P are quoted. This quoting is performed in the same way as for GNU ls. This is not the same quoting mechanism as the one used for -ls and -fls. If you are able to decide what format to use for the output of find then it is normally better to use `\0' as a terminator than to use newline, as file names can contain white space and newline characters. The setting of the `LC_CTYPE' envi‐ ronment variable is used to determine which characters need to be quoted. -print, -fprint Quoting is handled in the same way as for -printf and -fprintf. If you are using find in a script or in a situation where the matched files might have arbitrary names, you should consider using -print0 instead of -print. The -ok and -okdir actions print the current filename as-is. This may change in a future release. OPERATORS Listed in order of decreasing precedence: ( expr ) Force precedence. Since parentheses are special to the shell, you will normally need to quote them. Many of the examples in this manual page use backslashes for this purpose: `\(...\)' instead of `(...)'. ! expr True if expr is false. This character will also usually need pro‐ tection from interpretation by the shell. -not expr Same as ! expr, but not POSIX compliant. expr1 expr2 Two expressions in a row are taken to be joined with an implied "and"; expr2 is not evaluated if expr1 is false. expr1 -a expr2 Same as expr1 expr2. expr1 -and expr2 Same as expr1 expr2, but not POSIX compliant. expr1 -o expr2 Or; expr2 is not evaluated if expr1 is true. expr1 -or expr2 Same as expr1 -o expr2, but not POSIX compliant. expr1 , expr2 List; both expr1 and expr2 are always evaluated. The value of expr1 is discarded; the value of the list is the value of expr2. The comma operator can be useful for searching for several differ‐ ent types of thing, but traversing the filesystem hierarchy only once. The -fprintf action can be used to list the various matched items into several different output files. STANDARDS CONFORMANCE For closest compliance to the POSIX standard, you should set the POSIXLY_CORRECT environment variable. The following options are speci‐ fied in the POSIX standard (IEEE Std 1003.1, 2003 Edition): -H This option is supported. -L This option is supported. -name This option is supported, but POSIX conformance depends on the POSIX conformance of the system's fnmatch(3) library function. As of findutils-4.2.2, shell metacharacters (`*', `?' or `[]' for example) will match a leading `.', because IEEE PASC interpreta‐ tion 126 requires this. This is a change from previous versions of findutils. -type Supported. POSIX specifies `b', `c', `d', `l', `p', `f' and `s'. GNU find also supports `D', representing a Door, where the OS pro‐ vides these. -ok Supported. Interpretation of the response is according to the "yes" and "no" patterns selected by setting the `LC_MESSAGES' environment variable. When the `POSIXLY_CORRECT' environment variable is set, these patterns are taken system's definition of a positive (yes) or negative (no) response. See the system's docu‐ mentation for nl_langinfo(3), in particular YESEXPR and NOEXPR. When `POSIXLY_CORRECT' is not set, the patterns are instead taken from find's own message catalogue. -newer Supported. If the file specified is a symbolic link, it is always dereferenced. This is a change from previous behaviour, which used to take the relevant time from the symbolic link; see the HISTORY section below. -perm Supported. If the POSIXLY_CORRECT environment variable is not set, some mode arguments (for example +a+x) which are not valid in POSIX are supported for backward-compatibility. Other predicates The predicates -atime, -ctime, -depth, -group, -links, -mtime, -nogroup, -nouser, -print, -prune, -size, -user and -xdev are all supported. The POSIX standard specifies parentheses `(', `)', negation `!' and the `and' and `or' operators ( -a, -o). All other options, predicates, expressions and so forth are extensions beyond the POSIX standard. Many of these extensions are not unique to GNU find, however. The POSIX standard requires that find detects loops: The find utility shall detect infinite loops; that is, entering a previously visited directory that is an ancestor of the last file encountered. When it detects an infinite loop, find shall write a diagnostic message to standard error and shall either recover its position in the hierarchy or terminate. GNU find complies with these requirements. The link count of directories which contain entries which are hard links to an ancestor will often be lower than they otherwise should be. This can mean that GNU find will sometimes optimise away the visiting of a subdirectory which is actually a link to an ancestor. Since find does not actually enter such a subdi‐ rectory, it is allowed to avoid emitting a diagnostic message. Although this behaviour may be somewhat confusing, it is unlikely that anybody actually depends on this behaviour. If the leaf optimisation has been turned off with -noleaf, the directory entry will always be examined and the diagnostic message will be issued where it is appropriate. Symbolic links cannot be used to create filesystem cycles as such, but if the -L option or the -follow option is in use, a diagnostic message is issued when find encounters a loop of symbolic links. As with loops containing hard links, the leaf optimisation will often mean that find knows that it doesn't need to call stat() or chdir() on the symbolic link, so this diagnostic is frequently not necessary. The -d option is supported for compatibility with various BSD systems, but you should use the POSIX-compliant option -depth instead. The POSIXLY_CORRECT environment variable does not affect the behaviour of the -regex or -iregex tests because those tests aren't specified in the POSIX standard. ENVIRONMENT VARIABLES LANG Provides a default value for the internationalization variables that are unset or null. LC_ALL If set to a non-empty string value, override the values of all the other internationalization variables. LC_COLLATE The POSIX standard specifies that this variable affects the pat‐ tern matching to be used for the -name option. GNU find uses the fnmatch(3) library function, and so support for `LC_COLLATE' depends on the system library. This variable also affects the interpretation of the response to -ok; while the `LC_MESSAGES' variable selects the actual pattern used to interpret the response to -ok, the interpretation of any bracket expressions in the pat‐ tern will be affected by `LC_COLLATE'. LC_CTYPE This variable affects the treatment of character classes used in regular expressions and also with the -name test, if the system's fnmatch(3) library function supports this. This variable also affects the interpretation of any character classes in the regular expressions used to interpret the response to the prompt issued by -ok. The `LC_CTYPE' environment variable will also affect which characters are considered to be unprintable when filenames are printed; see the section UNUSUAL FILENAMES. LC_MESSAGES Determines the locale to be used for internationalised messages. If the `POSIXLY_CORRECT' environment variable is set, this also determines the interpretation of the response to the prompt made by the -ok action. NLSPATH Determines the location of the internationalisation message cata‐ logues. PATH Affects the directories which are searched to find the executables invoked by -exec, -execdir, -ok and -okdir. POSIXLY_CORRECT Determines the block size used by -ls and -fls. If POSIXLY_COR‐ RECT is set, blocks are units of 512 bytes. Otherwise they are units of 1024 bytes. Setting this variable also turns off warning messages (that is, implies -nowarn) by default, because POSIX requires that apart from the output for -ok, all messages printed on stderr are diag‐ nostics and must result in a non-zero exit status. When POSIXLY_CORRECT is not set, -perm +zzz is treated just like -perm /zzz if +zzz is not a valid symbolic mode. When POSIXLY_CORRECT is set, such constructs are treated as an error. When POSIXLY_CORRECT is set, the response to the prompt made by the -ok action is interpreted according to the system's message catalogue, as opposed to according to find's own message transla‐ tions. TZ Affects the time zone used for some of the time-related format directives of -printf and -fprintf. EXAMPLES find /tmp -name core -type f -print | xargs /bin/rm -f Find files named core in or below the directory /tmp and delete them. Note that this will work incorrectly if there are any filenames contain‐ ing newlines, single or double quotes, or spaces. find /tmp -name core -type f -print0 | xargs -0 /bin/rm -f Find files named core in or below the directory /tmp and delete them, processing filenames in such a way that file or directory names contain‐ ing single or double quotes, spaces or newlines are correctly handled. The -name test comes before the -type test in order to avoid having to call stat(2) on every file. find . -type f -exec file '{}' \; Runs `file' on every file in or below the current directory. Notice that the braces are enclosed in single quote marks to protect them from inter‐ pretation as shell script punctuation. The semicolon is similarly pro‐ tected by the use of a backslash, though single quotes could have been used in that case also. find / \ \( -perm -4000 -fprintf /root/suid.txt %#m %u %p\n \) , \ \( -size +100M -fprintf /root/big.txt %-10s %p\n \) Traverse the filesystem just once, listing setuid files and directories into /root/suid.txt and large files into /root/big.txt. find $HOME -mtime 0 Search for files in your home directory which have been modified in the last twenty-four hours. This command works this way because the time since each file was last modified is divided by 24 hours and any remain‐ der is discarded. That means that to match -mtime 0, a file will have to have a modification in the past which is less than 24 hours ago. find /sbin /usr/sbin -executable \! -readable -print Search for files which are executable but not readable. find . -perm 664 Search for files which have read and write permission for their owner, and group, but which other users can read but not write to. Files which meet these criteria but have other permissions bits set (for example if someone can execute the file) will not be matched. find . -perm -664 Search for files which have read and write permission for their owner and group, and which other users can read, without regard to the presence of any extra permission bits (for example the executable bit). This will match a file which has mode 0777, for example. find . -perm /222 Search for files which are writable by somebody (their owner, or their group, or anybody else). find . -perm /220 find . -perm /u+w,g+w find . -perm /u=w,g=w All three of these commands do the same thing, but the first one uses the octal representation of the file mode, and the other two use the symbolic form. These commands all search for files which are writable by either their owner or their group. The files don't have to be writable by both the owner and group to be matched; either will do. find . -perm -220 find . -perm -g+w,u+w Both these commands do the same thing; search for files which are writable by both their owner and their group. find . -perm -444 -perm /222 ! -perm /111 find . -perm -a+r -perm /a+w ! -perm /a+x These two commands both search for files that are readable for everybody ( -perm -444 or -perm -a+r), have at least one write bit set ( -perm /222 or -perm /a+w) but are not executable for anybody ( ! -perm /111 and ! -perm /a+x respectively). cd /source-dir find . -name .snapshot -prune -o \( \! -name *~ -print0 \)| cpio -pmd0 /dest-dir This command copies the contents of /source-dir to /dest-dir, but omits files and directories named .snapshot (and anything in them). It also omits files or directories whose name ends in ~, but not their contents. The construct -prune -o \( ... -print0 \) is quite common. The idea here is that the expression before -prune matches things which are to be pruned. However, the -prune action itself returns true, so the following -o ensures that the right hand side is evaluated only for those directo‐ ries which didn't get pruned (the contents of the pruned directories are not even visited, so their contents are irrelevant). The expression on the right hand side of the -o is in parentheses only for clarity. It emphasises that the -print0 action takes place only for things that didn't have -prune applied to them. Because the default `and' condition between tests binds more tightly than -o, this is the default anyway, but the parentheses help to show what is going on. find repo/ -exec test -d {}/.svn -o -d {}/.git -o -d {}/CVS ; \ -print -prune Given the following directory of projects and their associated SCM admin‐ istrative directories, perform an efficient search for the projects' roots: repo/project1/CVS repo/gnu/project2/.svn repo/gnu/project3/.svn repo/gnu/project3/src/.svn repo/project4/.git In this example, -prune prevents unnecessary descent into directories that have already been discovered (for example we do not search project3/src because we already found project3/.svn), but ensures sibling directories (project2 and project3) are found. EXIT STATUS find exits with status 0 if all files are processed successfully, greater than 0 if errors occur. This is deliberately a very broad description, but if the return value is non-zero, you should not rely on the correct‐ ness of the results of find. SEE ALSO locate(1), locatedb(5), updatedb(1), xargs(1), chmod(1), fnmatch(3), regex(7), stat(2), lstat(2), ls(1), printf(3), strftime(3), ctime(3), Finding Files (on-line in Info, or printed). HISTORY As of findutils-4.2.2, shell metacharacters (`*', `?' or `[]' for exam‐ ple) used in filename patterns will match a leading `.', because IEEE POSIX interpretation 126 requires this. The syntax -perm +MODE was deprecated in findutils-4.2.21, in favour of -perm /MODE. As of findutils-4.3.3, -perm /000 now matches all files instead of none. Nanosecond-resolution timestamps were implemented in findutils-4.3.3. As of findutils-4.3.11, the -delete action sets find's exit status to a nonzero value when it fails. However, find will not exit immediately.  Feature Added in Also occurs in -newerXY 4.3.3 BSD -D 4.3.1 -O 4.3.1 -readable 4.3.0 -writable 4.3.0 -exe‐ cutable 4.3.0 -regextype 4.2.24 -exec ... + 4.2.12 POSIX -execdir 4.2.12 BSD -okdir 4.2.12 -samefile 4.2.11 -H 4.2.5 POSIX -L 4.2.5 POSIX -P 4.2.5 BSD -delete 4.2.3 -quit 4.2.3 -d 4.2.3 BSD -whole‐ name 4.2.0 -iwholename 4.2.0 -ignore_readdir_race 4.2.0 -fls 4.0 -ilname 3.8 -iname 3.8 -ipath 3.8 -iregex 3.8 NON-BUGS $ find . -name *.c -print find: paths must precede expression Usage: find [-H] [-L] [-P] [-Olevel] [-D help|tree|search|stat|rates|opt|exec] [path...] [expression] This happens because *.c has been expanded by the shell resulting in find actually receiving a command line like this: find . -name bigram.c code.c frcode.c locate.c -print That command is of course not going to work. Instead of doing things this way, you should enclose the pattern in quotes or escape the wild‐ card: $ find . -name \*.c -print BUGS There are security problems inherent in the behaviour that the POSIX standard specifies for find, which therefore cannot be fixed. For exam‐ ple, the -exec action is inherently insecure, and -execdir should be used instead. Please see Finding Files for more information. The environment variable LC_COLLATE has no effect on the -ok action. The best way to report a bug is to use the form at http://savan‐ nah.gnu.org/bugs/?group=findutils. The reason for this is that you will then be able to track progress in fixing the problem. Other comments about find(1) and about the findutils package in general can be sent to the bug-findutils mailing list. To join the list, send email to<EMAIL_ADDRESS>FIND(1)


See: Description
| Interface | Description |
|---|---|
| JeeConfig |
Because sometimes you don't care about the difference between a
servlet and a filter.
|
| ViewContext |
This interface provides view tools in a servlet environment
access to relevant context information, like servlet request, servlet
context and the velocity context.
|
| Class | Description |
|---|---|
| AbstractSearchTool |
Abstract view tool for doing "searching" and robust
pagination of search results.
|
| AbstractSearchTool.StoredResults |
Simple utility class to hold a criterion and its result list.
|
| BreadcrumbTool |
Helper tool to display a navigation breadcrumb to the end user.
|
| BreadcrumbTool.NavigationElement |
Class representing a navigation element
|
| BrowserTool |
Browser sniffing tool (session or request scope requested, session scope advised).
|
| BrowserToolDeprecatedMethods | Deprecated |
| CookieTool |
View tool for convenient cookie access and creation.
|
| CookieTool.SugarCookie |
Extends
Cookie to add some fluid API sugar and
a toString() method that renders the Cookie's value
instead of the usual Object.toString() shenanigans. |
| ImportTool |
General-purpose text-importing view tool for templates.
|
| IncludeTool |
Allows for transparent content negotiation in a manner mimicking
Apache httpd's MultiViews.
|
| JeeContextConfig |
Implements
JeeConfig with only a ServletContext . |
| JeeFilterConfig |
Implements
JeeConfig with a FilterConfig . |
| JeeServletConfig |
Implements
JeeConfig with a ServletConfig . |
| JsonTool |
View version of
JsonTool . |
| LinkTool |
The LinkTool provides many methods to work with URIs and can help you:
construct full URIs (absolute or relative)
encode session ID into a URI
retrieve server, port and path info for the current request
reconstruct or alter the current request URI
and more..
|
| PagerTool |
View tool for doing request-based pagination of
items in an a list.
|
| ParameterTool |
Utility class for easy parsing of
ServletRequest parameters. |
| ServletUtils |
A set of utility methods for supporting and using
VelocityTools in the servlet environment.
|
| UAParser | |
| UAParser.UAEntity | |
| UAParser.UserAgent | |
| UiDependencyTool |
NOTE: This tool is considered "beta" quality due to lack of public testing
and is not automatically provided via the default tools.xml file.
|
| UiDependencyTool.FileRule |
NOTE: This class may change or disappear w/o warning; don't depend
on it unless you're willing to update your code whenever this changes.
|
| UiDependencyTool.GroupRule |
NOTE: This class may change or disappear w/o warning; don't depend
on it unless you're willing to update your code whenever this changes.
|
| UiDependencyTool.NeedsRule |
NOTE: This class may change or disappear w/o warning; don't depend
on it unless you're willing to update your code whenever this changes.
|
| UiDependencyTool.TypeRule |
NOTE: This class may change or disappear w/o warning; don't depend
on it unless you're willing to update your code whenever this changes.
|
| VelocityLayoutServlet |
Extension of the VelocityViewServlet to perform "two-pass"
layout rendering and allow for a customized error screen.
|
| VelocityView |
The class provides the following features:
|
| VelocityViewFilter |
A filter to ensure VelocityTools
Toolbox es are
available in the request/session/application scopes. |
| VelocityViewServlet |
A servlet to process Velocity templates.
|
| ViewContextTool |
Extension of
ContextTool that includes keys and values
from the HttpServletRequest , HttpSession and
ServletContext . |
| ViewImportSupport |
Provides methods to import arbitrary local or remote resources as strings.
|
| ViewImportSupport.ImportResponseWrapper |
Wraps responses to allow us to retrieve results as Strings.
|
| ViewImportSupport.SafeClosingHttpURLConnectionReader | |
| ViewToolContext |
ToolContext implementation specific to the servlet environment. |
| ViewToolManager |
Manages tools for web applications.
|
| WebappResourceLoader |
Resource loader that uses the ServletContext of a webapp to
load Velocity templates.
|
| WebappUberspector |
This custom uberspector allows getAttribute() and setAttribute() as standard
getters and setters for the "request","session" and "application" keys.
|
| XmlTool |
View version of
XmlTool . |
| Enum | Description |
|---|---|
| UAParser.DeviceType |
Copyright © 2002–2021 The Apache Software Foundation. All rights reserved.


From Excel to package.xml
Cleaning up an org that has gone through several generations of ownership and objectives is fun. Some tooling helps
Data frugality
A computing principle, very much the anathema to Google and Facebook, is Data Frugality, storing only what you actually need. It is the data equivalent to coders' YAGNI principle. Latest since GDPR it got center stage attention.
Your cleanup plan
So your cleanup exercise has a few steps:
- Find fields that don't have any data. You can use tools like Field Trip to achieve that
- Verify that these fields are not "about to be used", but "really obsolete"
- Add all the fields that did have some data left over, but unused now
- Add fields that contain data legal told you to get rid off
The absolute standard approach, of any consultant I have encountered, is to fire up an Excel sheet and track all fields in a list, capture insights in the remarks
column and have another column that indicates can be deleted
Status. Something like Yes,No,Investigating
or "Call Paul to clarify". I would be surprised if there's a different approach in the wild (in theory there are).
Excel as source?
In a current project the consultant neatly created one sheet (that's the page, not the file) per object, labeled with the object name, containing rows for all custom fields. Then the team went off to investigate. In result they identified more than one thousand fields to be deleted.
Now to actually get rid of the fields, you could outsource some manual labor to either go into you org or use Copy-Paste to create a destructivechanges.xml
package file for use with the Salesforce ANT tool.
In any case: the probability that there will be errors in transferring is approximately 100%. The business owner will point to: I signed off that spreadsheet and not that XML file! Finger pointing commencing.
There must be a better way
Read more
Posted by Stephan H Wissel on 23 February 2019 | Comments (0) | categories: Salesforce XML


[4] Devanand, T., Susmita Ghosh, Prasanna Venkatraman, and Satyavani Vemparala. “Phosphorylation of interfacial phosphosite leads to increased binding of Rap-Raf complex” bioRxiv doi: https://doi.org/10.1101/2<IP_ADDRESS>3331 (2021); [3] Susmita Ghosh, Devanand, T., Upayan Baul, and Satyavani Vemparala. “Aggregation dynamics of charged peptides in water: Effect of salt concentration.” J. Chem. Phys. 151, 074901 (2019); [2] Devanand, T., Sankaran Krishnaswamy, and Satyavani Vemparala. “Interdigitation of lipids induced by membrane active proteins.” The Journal of Membrane Biology (2019): 1-12. [1] Devanand, T., Prasanna Venkatraman, and Satyavani Vemparala. “Phosphorylation promotes binding affinity of Rap-Raf complex by allosteric modulation of switch loop dynamics.” Scientific reports 8.1 (2018): 12976.