The task in this activity was to create a pacman on demand (button click) and move these pacmen across the page.
Code RepoIn this Project, the MBTA bus data was used to determine stops between Harvard and MIT. Then, an animated marker was added on the map to highlight the bus routes.
Code RepoThe goal of this project was to interactively move the eyes based on the mouse position.
Code Repo


Pathfinders.Ai is an Australian based and owned consultancy that prides itself on its ability to drive results for our customers. We begin the exploration journey with you by ensuring we capture all your Business and technical requirements. These requirements are delivered to you and together we ensure their correctness. We use subject matter experts in every stage of your project and not just a one fit all approach, as we know every Business is different and so is every customer.
We gain an understanding of your Organisation’s top priorities, and show you how AI & ML can introduce new revenue channels, decrease costs, and improve productivity leading to significant return on investment (ROI) and Business benefits
Our skilled of Machine Learning and IT experts will work with your IT and Business during the design, build and deployment phases of your project and will ensure all our work and your IP is handed over and left with you.
In addition to this we offer a managed service where we can maintain your code and application and work with you on all future releases. It’s your choice…
Work with a team of highly experienced consultants and data scientists to establish best AI practice


{% extends "registration/base_form.html" %} {% block title %}Login{% endblock %} {% block form_header %}Login{% endblock %} {% block form_extra %} Forgot your password? Don't have an account yet? Register for an account first! {% endblock %}


All Classes
-
All Classes Interface Summary Class Summary Exception Summary Class Description Activity The Activity representation in the calendar of NOVA.ActivityCard An UI component that displays information of anActivity
.ActivityListPanel Panel containing the list of persons.ActivityNotFoundException Signals that the operation is unable to find the specified activity (Activities are considered not found if the date and time are the same).ActivityReference The entity used to reference to an activity using only the date and start time.AddCommand Represents the command to add an activity into the calendar of NOVA.AddCommandParser Parses input arguments and creates a new AddCommand objectAddTaskCommand Represents the command to add a task into the calendar of NOVA.AddTaskCommandParser AppParameters Represents the parsed command-line parameters given to the application.AppUtil A container for App specific utility functionsArgumentMultimap Stores mapping of prefixes to their respective arguments.ArgumentTokenizer Tokenizes arguments string of the form:preamble <prefix>value <prefix>value ...
e.g.Calendar The Calendar feature within NOVA.CalendarConstants The class to hold all the constants of calendar.CalendarStorage CollectionUtil Utility methods related to CollectionsCommand Represents a command with hidden internal logic and the ability to be executed.CommandBox The UI component that is responsible for receiving user command inputs.CommandBox.CommandExecutor Represents a function that can execute commands.CommandException Represents an error which occurs during execution of aCommand
.CommandResult Represents the result of a command execution.CompleteTaskCommand Represents the command to mark a specified task as completed.CompleteTaskCommandParser Config Config values used by the appConfigUtil A class for accessing the Config File.DataConversionException Represents an error during conversion of data from one format to anotherDay The day representation within the calendar of NOVA.DeleteCommand Represents the command to delete an activity from the calendar in NOVA.DeleteCommandParser Parses input arguments and creates a new DeleteCommand objectDeleteTaskCommand Represents the command to delete a task from the calendar of NOVA.DeleteTaskCommandParser DuplicateActivityException Signals that the operation will result in duplicated Activities (Activities are considered not found if the date and time are the same).ExitCommand Represents the command to terminate the program.FileUtil Writes and reads filesGuiSettings A Serializable class that contains the GUI settings.HelpCommand Represents the command to format full help instructions for every command for display.HelpWindow Controller for a help pageIllegalValueException Signals that some given data does not fulfill some constraints.Index Represents a zero-based or one-based index.JsonAdaptedActivity JsonAdaptedTask JsonCalendarStorage JsonSerializableCalendar JsonUserPrefsStorage A class to access UserPrefs stored in the hard disk as a json fileJsonUtil Converts a Java object instance to JSON and vice versaLesson The Lesson type activity representation to mark school lessons in the calendar of NOVA.Logic API of the Logic componentLogicManager The main LogicManager of the app.LogsCenter Configures and manages loggers and handlers, including their logging level NamedLogger
s can be obtained from this class
These loggers have been configured to output messages to the console and a.log
file by default, at theINFO
level.Main The main entry point to the application.MainApp Runs the application.MainWindow The Main Window.Meeting The Meeting type activity representation to mark important meetings in the calendar of NOVA.Messages Container for user visible messages.Model The API of the Model component.ModelManager Represents the in-memory model of the address book data.NextActivityCard An UI component that displays information of the next occuring activity.NovaParser Parses user input.ParseException Represents a parse error encountered by a parser.Parser<T extends Command> Represents a Parser that is able to parse user input into aCommand
of typeT
.ParserUtil Contains utility methods used for parsing strings in the various *Parser classes.Prefix A prefix that marks the beginning of an argument in an arguments string.PrefixConstants Contains Command Line Interface (CLI) syntax definitions common to multiple commandsReadOnlyCalendar The interface for all getters and utility methods.ReadOnlyUserPrefs Unmodifiable view of user prefs.RepeatedCompleteException ResetCommand Represents the command to reset the calendar to a clean slate and adjust the period of the calendar to start on the user specified start date.ResetCommandParser ResultDisplay A ui for the status bar that is displayed at the header of the application.SampleDataUtil Contains utility methods for populatingNOVA
with sample data.StatisticCard Represents the display cards for statistics in NOVA.Storage API of the Storage componentStorageManager Manages storage of NOVA's data in local storage.StringUtil Helper functions for handling strings.Task The Task representation to track important task to complete in the calendar of NOVA.TaskCard TaskCompletionCard An UI component that displays information of the completion status of the tasks in the calendar.TaskCompletionStatistics The data structure to represent the statistics of task completion.TaskListPanel TaskReference The entity used to reference to a task using only the date and start time.Ui API of UI componentUiManager The manager of the UI component.UiPart<T> Represents a distinct part of the UI.UniqueActivityList A list of activities that enforces uniqueness between its elements and does not allow nulls.UniqueTaskList A list of tasks that enforces uniqueness between its elements and does not allow nulls.UserPrefs Represents User's preferences.UserPrefsStorage Represents a storage forUserPrefs
.Version Represents a version with major, minor and patch numberViewCommand Represents the command to Views all activities of a date.ViewCommandParser The type View command parser.Week The week representation within the calendar of NOVA.WeekNumberCard An UI component that displays information of the current week in accordance to the semester.


Willing to relocate • Authorized to work in the US for any employer • Native English speaker
To facilitate a group of people, into working collaboratively, toward the completion of project goals.
sql
css3
ruby
html5
javascript
git
linux
github
react js
speaking
bootstrap
ruby on rails 5
microsoft 2016: excel, visio, word
THE MINISTRY CONCIERGE, INC.
January 2017 – Present
Manage websites • Maintained and updated legacy code • Developed websites applications • Content management
SENTRY EVENT SERVICES, INC
September 2017 – 2018
Greeted event participants and assisted participants with seating • Performed on-demand conflict resolution • Assisted with post event clean-up
THE MINISTRY CONCIERGE, INC.
January 2014 – 2015
Greeted seminar participants and assisted them with the registration process • Preformed on-demand research • Assisted with post seminar clean-up
GED W/ HONORS CO’ 2016
Marianna Adult Education Center


| First Name | Last Name | Contact Number | Country | Source | Buying Purpose | Interest Level | Preferred Size | Notes | ClientID | TeamID | ||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| First Name | Last Name | Contact Number | Country | Source | Buying Purpose | Interest Level | Preferred Size | Notes | ClientID | TeamID |
| ProjectID | Unit | Project Name | Estimated Amount | Buying Stage | ClientID | AccountID |
|---|---|---|---|---|---|---|
| Please select a client from the table above to manage. | ||||||
| ProjectID | Unit | Project Name | Estimated Amount | Buying Stage | ClientID | AccountID |
| ProjectID | Unit | Project Name | Final Amount | Buying Stage | ClientID | AccountID |
|---|---|---|---|---|---|---|
| Please select a client from the table above to manage. | ||||||
| ProjectID | Unit | Project Name | Final Amount | Buying Stage | ClientID | AccountID |


The Brief: a time-travel trip in a Trabant - 'Ostalgia' in Brussels
by Sandor Zsiros, Meabh McMahon, Laura Ruiz TrullolsThirty years after the fall of the Berlin fall people still think there are lessons to be learned from socialism.
We met with a Portuguese man living in Brussels who owns a Trabant, the iconic car from East Germany. He says some aspects of the socialist economy are worth reconsidering.
"I am not saying that the socialist model in East Germany was ideal. But we must at least stop for a minute to think if there are other models that are possible. For example this was a model (trabi) that was designed in the late 50s and was produced with minor changes until 1991. And nowadays we buy a car and change it every three years and every three years the brand will release a new version of their car and I don't find it particularly sustainable," José Gonçalves told Euronews.
But this doesn't herald an ideological return.
"I don't think that people would like to go back to East German socialism. This is not the question," Martin Schirdewan, German MEP explains.
"It is about the fact that today's society needs to become more social and that the GDR and life in East Germany had achieved a higher degree of equality. I believe that we need to start talking to each other about the GDR and about German re-unification in a much more differentiated way."
Commission impossible?
Three more candidates will head to hearings this week hoping to join Team Ursula. The Romanian, Hungarian and French nominees will face a grilling from MEPs on Thursday. If they pass the test, their candidatures will be put to vote before the full parliament with the aim of the new commission taking up their posts from December.
And also...EU top court rules on Israeli settlement products
The EU's top court has ruled that products from Israeli settlements must be labelled as such, in a decision likely to anger Tel Aviv but largely welcomed by human rights groups.
"Foodstuffs originating in the territories occupied by the State of Israel must bear the indication of their territory of origin, accompanied, where those foodstuffs come from an Israeli settlement within that territory, by the indication of that provenance" the ruling stated.


This Summer we invited the world's famous jitterbugs Pol Prats and Sara Planas to London to share some of their favourite recipes how to make the crowd cheer and scream! Over the two days we will learn how to cook hot spicy Aerial Steps and delicious juicy Shag moves.
Be ready for the best mix of ingredients to put some flavour to your Aerials menu! The starter is a 10-15 minutes warm up followed by 4-6 aerials that will leave your mouth open. Our menu doesn't offer the standard ones like "around the back". Instead we focus on the original recipes, some traditional aerials and some more modern. Our ingredients are perfect to be blended with Shag or Lindy.
We won’t rotate in this class so you will need to find a partner who you trust and have danced with before. This is an improvers / intermediate level aerials workshop. Some experience would be recommended.
The first 2 hours section will start with our basics but breathtaking aerial steps. The second 2 hours section will continue with the main special ones.
Workshop capacity: 10 couples only!
Dress code:
Prices:
Our chefs Pol and Sara will share some of the Spanish secrets that will give to your Shag the right seasoning.
Main course features the super stars from the Barcelona Shag Festival. These two amazing Shag specialists have developed a very special and unique style full of spicy combo steps.
Be careful! The dishes will get so savory that we advise you attend only if you are able to dance Shag socially thus workshop is directed to intermediate and advanced levels.
Workshop capacity: 35 people only!
Dress code:
Prices:
For more information and updates please see Salty Recipes ☆ Aerials / Shag with Pol & Sara.


To demonstrate Java EE 7 technologies
To provide developers with working examples and instructions that are easy to follow .
To allow examples to be copied by developers and used as the basis for their own projects.
To contribute to the quickstarts, fork the quickstart repository to your own Git, clone your fork, commit your work on topic branches, and make pull requests.
If you don't have the Git client (git
), get it from: http://git-scm.com/
Here are the steps in detail:
Fork the project. This creates a the project in your own Git with the default remote name 'origin'.
Clone your fork. This creates and populates a directory in your local file system.
git clone git@github.com:<your-username>/quickstart.git
Add the remote upstream
repository so you can fetch any changes to the original forked repository.
git remote add upstream git@github.com:wildfly/quickstart.git
Get the latest files from the upstream
repository.
git fetch upstream
Create a new topic branch to contain your features, changes, or fixes using the git checkout -b <topic-branch-name> upstream/master
command. For example:
git checkout -b helloworld-fix upstream/master
Contribute new code or make changes to existing files. Make sure that you follow the General Guidelines below.
To verify if your code followed the General Guidelines you can run QS Tools on your project.
mvn -U org.jboss.maven.plugins:maven-qstools-plugin:check
This will generate a report on QUICKSTART_HOME/target/site/qschecker.html
. Review the report to determine if your quickstart project violates any item in the General Guidelines.
git add
command to add new or changed file contents to the staging area. git add src/
git add pom.xml
git add README.md
Note: It is probably best not to add the entire quickstart root folder because you may unintentionally add classes or other target files that should not be in source control.
* If you only modified a few files, use git add <filename>
for every file you create or change. For example:
git add README.md
Use the git status command to view the status of the files in the directory and in the staging area and ensure that all modified files are properly staged:
git status
Commit your changes to your local topic branch.
git commit -m 'Description of change...'
Push your local topic branch to your github forked repository. This will create a branch on your Git fork repository with the same name as your local topic branch name.
git push origin HEAD
Note: The above command assumes your remote repository is named 'origin'. You can verify your forked remote repository name using the command git remote -v
. 12. Browse to the
The sample project should be formatted using the WildFly profiles found at http://github.com/jboss/ide-config/tree/master/
Code should be well documented with good comments. Please add an author tag (@author) to credit yourself for writing the code.
The package must be org.wildfly.quickstarts
The quickstart project or folder name should match the quickstart name. Each sample project should have a unique name, allowing easy identification by users and developers.
The quickstart project <artifactId>
in the pom.xml
file must be prefixed by wildfly-
. For example, the <artifactId>
for a is-f-fast
quickstart is wildfly-is-f-fast
.
If you create a quickstart that uses a database table, make sure the name you use for the table is unique across all quickstarts.
The project must follow the structure used by existing quickstarts such as numberguess. A good starting point would be to copy the numberguess
project.
The sample project should be importable into JBoss Developer Studio/JBoss Tools and be deployable from there.
Maven POMs must be used. No other build system is allowed unless the purpose of the quickstart is to show another build system in use. If using Maven it should:
Not inherit from another POM
The sample project must contain a README.md
file using the template/README.md
file as a guideline
Don't forget to update the pom.xml
in the quickstart root directory. Add your quickstart to the 'modules' section.
The project must target Java 6
CDI should be used as the programming model
There are multiple quickstarts based on the kitchensink example. Each showcases different technologies and techniques including pure EE7, JSF, HTML5, and GWT.
If you wish to contribute a kitchensink variant is it important that you follow the look and feel of the original so that useful comparisons can be made. This does not mean that variants can not expand, and showcase additional functionality. Multiple variants already do that. These include mobile interfaces, push updates, and more.
Below are rules for the look and feel of the variants:
Follow the primary layout, style, and graphics of the original.
Projects can have 3-4 lines directly under the WildFly banner in the middle section to describe what makes this variant different.
Projects can have their logo in the left side of the banner.
If appropriate for the technology the application should expose RESTful endpoints following the example of the original kitchensink quickstart. This should also include the RESTful links in the member table.
The quickstart README.md files are converted to HTML using markdown. We recommend using redcarpet, as that is what github uses, but you can use any markdown tool really.
There are two scripts, dist/github-flaoured-markdown.rb
, that will convert an individual file, and dist/release-utils.sh -m
, that will convert all the files.
To setup the environment you need to follow these steps.
Install Ruby 1.9.X
For RHEL you can use this spec
In general, you're better off not relying on your OSs ruby install, they are often quite broken.
Install Ruby GEMs
gem install nokogiri pygments.rb redcarpet fileutils
Install Python Eggs
You'll need python eggs installed, which often isn't available on OS installs of python. Google to find out how to install it
Install pygments
sudo easy_install pygments
JBoss Developer Framework is licensed under the Apache License 2.0, as we believe it is one of the most permissive Open Source license. This allows developers to easily make use of the code samples in JBoss Developer Framework.
There is no need to sign a contributor agreement to contribute to JBoss Developer Framework. You just need to explicitly license any contribution under the AL 2.0. If you add any new files to JBoss Developer Framework, make sure to add the correct header.
/**
* JBoss, Home of Professional Open Source
* Copyright 2015, Red Hat, Inc. and/or its affiliates, and individual
* contributors by the @authors tag. See the copyright.txt in the
* distribution for a full listing of individual contributors.
*
* Licensed under the Apache License, Version 2.0 (the "License");
* you may not use this file except in compliance with the License.
* You may obtain a copy of the License at
* http://www.apache.org/licenses/LICENSE-2.0
* Unless required by applicable law or agreed to in writing, software
* distributed under the License is distributed on an "AS IS" BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
*/
<!--
JBoss, Home of Professional Open Source
Copyright 2015, Red Hat, Inc. and/or its affiliates, and individual
contributors by the @authors tag. See the copyright.txt in the
distribution for a full listing of individual contributors.
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-->
# JBoss, Home of Professional Open Source
# Copyright 2015, Red Hat, Inc. and/or its affiliates, and individual
# contributors by the @authors tag. See the copyright.txt in the
# distribution for a full listing of individual contributors.
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
# http://www.apache.org/licenses/LICENSE-2.0
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
--
-- JBoss, Home of Professional Open Source
-- Copyright 2015, Red Hat, Inc. and/or its affiliates, and individual
-- contributors by the @authors tag. See the copyright.txt in the
-- distribution for a full listing of individual contributors.
--
-- Licensed under the Apache License, Version 2.0 (the "License");
-- you may not use this file except in compliance with the License.
-- You may obtain a copy of the License at
-- http://www.apache.org/licenses/LICENSE-2.0
-- Unless required by applicable law or agreed to in writing, software
-- distributed under the License is distributed on an "AS IS" BASIS,
-- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-- See the License for the specific language governing permissions and
-- limitations under the License.
--
<%--
JBoss, Home of Professional Open Source
Copyright 2015, Red Hat, Inc. and/or its affiliates, and individual
contributors by the @authors tag. See the copyright.txt in the
distribution for a full listing of individual contributors.
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
--%>


Canonicalize all input used to identify resources, such as filenames, paths, named pipes, etc.
There are often many ways to address the same resource by name. An attacker may try to bypass validation routines to perform unauthorized access by supplying obfuscated input. Canonicalization defeats obfuscation and helps validate data access attempts.
Canonicalize all input used to identify resources before using it for access.
Canonicalization means reducing to the simplest form. There are often many ways to access the same resources by name. One example is addressing files - the same file on a Windows system may be addressed as file, C:\file, C:\\file, ..\file, ..\..\..\file, etc. Canonicalization is particularly important for systems that use unicode, because there are many different unicode strings that have the same meaning to the OS.
Perform the following actions to canonicalize all input used to identify resources:
Identify all functions used to access resources, such as files or folders, by name. On UNIX-type systems, named pipes and devices are other resources that may be accessed by name. Add code that canonicalizes and validates this input. It is recommended to create a separate class or library for data validation routines and include functions for canonicalizing input in it.
Use realpath() on POSIX systems. The POSIX C++ standard includes a realpath() function, which is suitable for canonicalization.
Use canonicalize_file_name() on glibc systems. Glibc includes a canonicalize_file_name() function, which works a lot like realpath(), but automatically allocated a new buffer for its output. Free the memory allocated by canonicalize_file_name() after canonicalization, because that is not done automatically.
Don't rely on canonicalization in Windows. Canonicalization in Windows is done by the GetFullPathName() function, however this function is very limited and provides a very low degree of assurance. Use ACLs on Windows to implement filesystem security and avoid making decisions based on file or folder names.
Avoid time-of-check-to-time-of-use vulnerabilities. Most Unix systems implement versions of common filesystem calls that use file handles instead of file names, such as openat, statat, accessat, etc. Use these functions instead of the ones that use filenames to avoid TOCTOU vulnerabilities.


September 27 |
Node.js/JavaScript |
September 11 |
Topic TBD |
November 10-11 |
Hackathon! (more info to come) |
ACM brings together computing educators, researchers, and professionals to inspire dialogue, share resources, and address the field's challenges. As the world’s largest computing society, ACM strengthens the profession's collective voice through strong leadership, promotion of the highest standards, and recognition of technical excellence. ACM supports the professional growth of its members by providing opportunities for life‐long learning, career development, and professional networking.
Founded at the dawn of the computer age, ACM’s reach extends to every part of the globe, with more than half of its 100,000 members residing outside the U.S. Its growing membership has led to Councils in Europe, India, and China, fostering networking opportunities that strengthen ties within and across countries and technical communities. Their actions enhance ACM’s ability to raise awareness of computing’s important technical, educational, and social issues around the world.


{% load static %}
Resolute QA
Projects
Summary
Run Results
{% for suite in suite_runs %}
{{ suite.suite.suite_name }}
{% endfor %}
Bugs
Upload
(current)
Admin
Project:
{{ projectenvironment.project }}
Environment:
{{ projectenvironment.environment }}
Upload Results
{% csrf_token %}


Features
|
|
Animacy
: animacy
This document is a placeholder for the language-specific documentation
for Animacy
.
Aspect
: aspect
This document is a placeholder for the language-specific documentation
for Aspect
.
Case
: case
Case is an inflectional feature of nouns and other parts of speech (adjectives, verbs, articles) that mark agreement with nouns.
In Irish four cases are used: common (which covers nominative and accusative case), vocative, genitive and dative. These cases are labelled respectively as NomAcc
, Voc
, Gen
, and Dat
.
NomAcc
: common case
The common case is the base form of the noun, and is used in the citation form (lemma). This word form is used for subjects and objects of a clause, and predicates of a copula.
Examples
Subjects:
- Tosóidh an cheolchoirm ar 8pm “The concert will start at 8pm”
- Chabhraigh an leon le Micí “The lion helped Mickey”
Objects:
- Cuireann Paul an píosa seo chugainn “Paul offers this piece to us”
- D’ith sí an dinnéar “She ate the dinner”
Predicates:
- is láithreán uafásach é seo “this is an awful site”
- Is múinteoir é “He is a teacher”
Voc
: vocative case
The vocative case is used to mark a noun as being the addresse. It is preceded by the particle a
. The vocative case triggers lenition in the word.
Examples
- ‘Slán leat, a Dhoráid! “Goodbye, Dorád!”
- a dhaoine uaisle “ladies and gentlemen”
Gen
: genitive case
The genitive case indicates possesion or ownership. It’s use is similar to the use of ’s in English. Other use cases include describing the composition of an object, compound nouns, or objects of a compound preposition.
Examples
- dearadh an stáitse “outloook of the state”
- mac an fhir “son of the man”
- an Aontais Eorpaigh “the European Union”
Dat
: dative case
The dative case is used with most simple prepositions in Irish. In standard Irish, the dative form is identical to the common case.
Examples
- in Eireann “in Ireland”
- le hEireann “with Ireland”
Definite
: definiteness or state
In Irish, definiteness is indicated through the use of a definite particle singular an or plural na (also used with feminine singular in genitive case, see below), much like the definite article “the” in English. There is no indefinite particle, with nouns considered indefinite unless otherwise indicated.
Def
: definite
Determiners an and na are both definite, as mentioned above.
The noun can also indicate definiteness, though treatment depends on case, gender and number.
Nominative case
In the nominative case (see Case) nouns undergo some changes following the definite article an; most feminine nouns are lenited after the definite article, while feminine nouns beginning with ‘s’ will become ‘ts’. Meanwhile, masculine nouns beginning with a vowel get the prefix ‘t-‘.
Following the plural definite article na, both masculine and feminine nouns beginning with a vowel receive the prefix ‘h’.
Examples
- an bua “the win”
- an fharraige “the sea”
- an tseachtain “the week”
- an t-aonad “the unit”
- na buntáistí “the advantages”
- na hábhair “the subjects”
Genitive
In the genitive case (see Case) the singular definite article an is only used with masculine nouns. In this case, masculine nouns behave like feminine nouns in the nominative case, most masculine nouns beginning with a consonant are lenited, and those beginning with a ‘s’ change to ‘ts’. However, nouns beginning with a vowel remain the same.
The plural definite article na is used with feminine singular nouns. In this case, feminine singular nouns beginning with a vowel are prefixed by ‘h’, while those beginning with a consonant don’t change. For plural nouns, na causes an eclipses where the nouns begin with a consonant. Plural nouns beginning with a vowel receive the prefix ‘-n’.
Examples
- imeachtaí an Éirí “activities of the successful”
- chumas an pháiste “ability of the child”
- biaiste an tsamhraidh “season of summer”
- thitim na hoíche “fall of the night”
- óga na tíre “young of the country”
- eagras na bhfostóirí “organisation of the employers”
- measc na n-ábhar “middle of the subjects”
Ind
: indefinite
There are no indefinite articles in Irish, however some nouns may inflect to show indefinite features.
Examples
- a gcuid uibheacha “her eggs”
- as láimh “out of hand”
Degree
: degree of comparison
Degree is a feature of adjectives that describe the quality of a noun.
Pos
: positive, first degree
States the quality of an object without comparing that quality to those of any other object.
Examples
Cmp
: comparative, second degree
Sup
: superlative, third degree
In Irish, the comparative and the superlative form is the same. In both cases, the adjective is written in the genitive case. Both the comparative and the superlative require a particle prefix. For the comparative degree, this is níos which corresponds to the English “more”. The superlative degree has particle is, which can be loosely translated as “the most”.
Examples
- níos fada “longer”
-
níos mó “bigger”
- is fearr “the best”
- is mó “the biggest”
Dialect
: Dialect
In Irish, three main dialects are found, with certain grammatical and lexical variations between the dialects. Words or grammatical features in the treebank which were judged to belong to a particular dialect were marked with the Dialect feature.
Connaught
: Connaught dialect
The Connaught dialect is the variety of Irish spoken mostly in the province of Connaught in the west of Ireland. Only one instance of Connaught dialect is currently present in the treebank.
Examples
- Caidé (standard: Cad é) “What is it”
Munster
: Munster dialect
The Munster dialect is the variety of Irish spoken mostly in the province of Munster in the south of Ireland. Most of the instances of dialect variation in the treebank are of Muster variety.
Examples
- Dhein sé (standard: rinne) “He did”
- so (standard: seo) “this”
- san (standard: sin) “that”
Ulster
: Ulster dialect
The Ulster dialect is the variety of Irish spoken mostly in the province of Ulster in the north of Ireland, mostly limited to the county of Donegal.
Examples
- domhsa (standard: dom) “for me”
- fá (standard: faoi) “under”
- cha (standard: ní) (negation)
Form
: Form
One of the characteristics of Irish is its tendency for initial mutation to occur in certain circumstances. This is triggered by the preceding word and affects the spelling of nouns, adjectives and verbs.
Ecl
: eclipsis
This feature occurs when the initial consonant or vowel of a word is eclipsed by a prefixing consonant. This is either a voiced consonant for voiceless consonants, or a nasalised consonant for voiced consonants. Vowels are eclipsed by adding n- or -t. Not every consonant can experience eclipsis.
Eclipsis will happen in a number of environments:
- after the plural possessive nouns ár, bhur and a (“our”, “your (pl.)”, “their”)
- on singular count nouns following the numbers 7-10
- after the preposition i “in”
- on plural nouns in the genitive case after the definite article
- on singular nouns in the dative case after the definite article
- following certain clitics such as interrogative particles (an, nach), complementisers (go, nach) and relativisers (a, nach)
Examples
- a gcuid iarrachtaí “their efforts”
- seacht mblian “seven years”
- i nGaeilge “in Irish”
- costas na n-oibreacha “cost of the works”
- ar an bhfocal “on the word”
- nach bhfaca sé “he didn’t see”
Emp
: emphatic
The emphatic form is a special form a word takes to mark the emphatic in Irish.
Examples
- dom “to me”
- domhsa “to me (emph)”
- a deirim “I said”
- a deirimse “I said (emph)”
Len
: lenition
Lenition is one of the most common means of initial mutation. When lenited, h is added immediately after the initial consonant.
These are some of the environments that trigger lenition:
- following the definite article (see Definite for specifics)
- following the vocative particle a
- after certain adjectives (singular possessive pronouns, uile, aon, dhá, etc.)
- after certain simple prepositions (a, de, do, faoi, etc.)
- following the past tense of the copula is
- following preverbal particles in the past tense (níor, ar, etc.)
- verb forms in the past tense
Examples
- an fharraige “the sea”
- A Dhochtúir Van Helsing “Doctor Van Helsing”
- mo chuid oibre “my work”
- faoi cheist “under question”
- Ba mhaith liom “I would like”
- Níor chuir sin “that doesn’t put”
- tháinig “came”
HPref
: h-prefix
In cases where a word causes neither lenition nor eclipsis and ends in a vowel, it will cause a h-prefix to attach the following word if that word begins with a vowel.
Examples
- go hálainn “lovely”
- na heisimirce “emigration”
- de h-Íde “from Íde”
- ní hamháin “not only”
VF
: Vowel form
Vowel form is an indicator of spelling changes that occur in copular verbs when followed by a word that begins with a vowel or a lenited consonant.
Examples
- is copula, “is”
- ab ea iad “they are”
- gurbh é “it was”
- B’fhearr leis lit. “it was better for him”
Gender
: gender
Irish has two gender forms: masculine and feminine.
Masc
: masculine gender
In general, words ending in a broad consonant are masculine. Exceptions include words ending in slender -óir, -eoir, and -ín, which are masculine.
Examples
- madra “dog”
- múinteoir “teacher”
Fem
: feminine gender
In general, words ending in a slender consonant are feminine. Exceptions include words ending in a broad -óg, or -eog, which are feminine.
Examples
- Éire “Ireland”
- néaróga “nerves”
Mood
: mood
Mood is a feature that expresses modality and subclassifies finite verb forms. It allows for a speaker to express their attitude towards what they are saying.
Ind
: indicative mood
The indicative mood can be considered the default form of a verb. A verb in the indicative indicates something that has happened, is happening or will happen.
Examples
- deirim “I say”
- Conas atá sé? “How is he?”
- Breacfaidh mé síos “I will jot down”
Cnd
: conditional mood
The conditional mood is used to express actions that are hypothetical or contrary to known fact. In Irish, the conditional is expressed in two different verb endings; these endings begin with the suffix -f- or -ó-. In all but the 3rd person singular and the 2nd person plural, the verb endings are synthetic and do not require a subject pronoun. Conditional clauses are often introduced using go or dá.

Examples
- Ná habair liom “Don’t tell me”
- bígí ar ais anseo “be back here”
- Chuiridís oilithrigh amach “let them send the pilgrims out”
Sub
: subjunctive mood
In Irish, the subjunctive mood is used to express a wish, or something that is not directly stated to be factual. It is normally formed with the particle go (positive) or nár (negative) followed by the verb in the subjunctive form. Sula ‘before’ is sometimes also used.
 Instead, a negative particle is used in combination with the verb to give a negative polarity.
The negative particle ní* is used before verbs in almost every tense, except the past. It causes lenition where this is possible, otherwise there is no change. In the past tense the particle is written as níor, and doesn’t affect the inflection.
The interrogative negative particle nach is used to pose a negative question.
The verb “to be” (in Irish bí) is given the negative form níl in the present tense, as a contraction of ní bhfuil. It can inflect to show (for instance) person.
*In the Ulster dialect, this particle also appears as cha (see Dialect)
Neg
: negative
Examples
- Ní thuigim “I don’t understand”
- Níor ól sé “He didn’t drink”
- Nach bhfuil tú? “Aren’t you?”
- Níl sé sin mí-réasúnta “That is not unreasonable”
- Ach nílirse sásta “But you aren’t happy”
NounType
: NounType
In Irish, noun forms fall into certain groups, that can change the spelling of the noun itself or surrounding words in certain contexts.
Strong
: strong plurals
The form of a strong plural remains unchanged regardless of grammatical case, i.e. it does not inflect.
Examples
- bláthanna “flowers” (nomacc, gen)
- oibreacha “works” (nomacc, gen)
- cótaí “coats” (nomacc, gen)
Weak
: weak plurals
Unlike the strong plural, a weak plural noun changes form depending on case.
Examples
- focail “words” (nomacc)
- focal “words” (gen)
- Aontais “Unions” (nomacc)
- Aontas “Unions” (gen)
Adjectives in Irish can have endings that are slender or not slender (broad). Depending on how the preceding noun ends, the form of the adjective can change.
NotSlender
: broad consonants
A final consonant is termed broad if the preceding vowel is broad (a, á, o, ó, u, ú).
Examples
- dathanna príomhúla
- nótaí praiticiúla
Slender
: slender consonants
A final consonant is termed slender if the preceding vowel is slender (e, é, i, í).
Examples
- na heagrais dheonacha
- thuaithe cháilitheacha
NumType
: numeral type
Irish numeral forms inflect to demonstrate different grammatical roles.
Card
: cardinal numbers
Cardinal numbers can be divided into those without nouns (used in counting, giving the time, etc.), and those with nouns. Those used without nouns use a particle a that is absent in those used with nouns.
Examples
Counting, etc.:
- a haon “one”
- a seacht “seven”
- a sé a chlog “six o’ clock”
Numbers qualifying nouns:
- dhá bhliain “two years”
- naoi gcapall déag “nineteen horses”
- seasca punt “sixty pounds”
Pers
: personal numerals
The personal numerals are used for counting people. From numbers 1-12 this system of counting differs from that used with other nouns, after that, the form is the same as the cardinal form, or a combination of the two forms.
Examples
- duine amháin “one person”
- beirt “two people”
- aon bhean dhéag “eleven women”
- seasca fear “sixty men”
Ord
: ordinal numbers
Ordinal numbers can be used to show order of items. In Irish, the form uses the definite particle an. (see Definite). The English abbreviation “th” appended to a numeral, is given in Irish as ú.
Examples
- an chéad lá “the first day”
- an dara dóigh “the second prospect”
- an 17ú Marta “the 17th of March”
Number
: number
Number is an inflectional feature of nouns and other parts of speech (determiners, adjectives, prepositions, verbs, etc.) that mark agreement with nouns. Words can be either singular or plural. Verb endings frequently inflect depending on number and person, across many moods and tenses.
Sing
: singular
A singular noun (or pronoun) denotes one person, animal or thing.
Examples
Adjectival agreement
- an duine rialta “the regular person”
- shruth leictreach ró-mhór “excessive electric current”
Verbal agreement
- deirim “I say”
- cheapfá “you would think”
- bíodh “be” (3rd person singular)
Plur
: plural
A plural noun (or pronoun) denotes several persons, animals or things.
Examples
Adjectival agreement
- fiacla sealadacha “temporary teeth”
- na himroeirí áitiúla “the local players”
- na focail crua “the cruel words”
Verbal agreement
- táimid “we are”
- bígí “be” (2nd person plural)
- chuireadar “they put”
PartType
: PartType
This document is a placeholder for the language-specific documentation
for PartType
.
Person
: person
Person is a feature of personal and possessive pronouns and verbs. In verbs, this feature marks the subject, in some cases allowing the subject to be dropped entirely. In Irish, some verbs are constructed synthetically, and some are analytically constructed.
1
: first person
The first person refers to the speaker; singular first person includes just one speaker, while plural first person includes many speakers, or groups the speaker with others. In Irish verbs, the first person forms a synthetic verb, where the subject pronoun may be dropped from the verb. Prepositional and possessive pronouns also inflect to denote person and number.
Examples
- Molaim a gcuid iarrachtaí. “I commend their efforts.”
- Chaitheamar roinnt urchar leo. “We shot several bullets at them.”
2
: second person
The second person refers to the listener. The singular first person denotes just one listener, while the plural form denotes several listeners. Verbs in Irish do not indicate 2nd person, so subject pronouns are necessary.
Examples
- An bhfeiceann tú “Do you see”
- Amharcaigí anois an méid atá déanta agam! “Look at the amount I’ve done!”
3
: third person
The third person refers to one or more persons who are not present, i.e. neither speakers nor listeners.
Examples
- Tugann sé neart eolais dúinn “He gives us plenty of information”
- Déanann siad poll “They make a hole”
Poss
: possessive
Boolean feature of pronouns, determiners or adjectives. It tells whether the word is possessive.
While many tagsets would have “possessive” as one of the various pronoun types, this feature is intentionally separate from PronType, as it is orthogonal to pronominal types. Several of the pronominal types can be optionally possessive, and adjectives can too.
Yes
: possessive
Note that there is no No value. If the word is not possessive, the Poss feature will just not be mentioned in the FEAT column. (Which means that empty value has the No meaning.)
Examples
PrepForm
: PrepForm
Cmpd
: compound preposition
In Irish, a simple preposition can be combined with a noun to give a compound preposition. Nouns following compound prepositions are inflected in the genitive case.
Examples
- tar éis “after”
- ar feadh “for” (length of time)
- de réir “according to”
PronType
: pronominal type
Art
: articles
Dem
: demonstrative
Ind
: indefinite
Int
: interrogative
Prs
: person
Rel
: relative
Reflex
: reflexive
Yes
: it is reflexive
The reflexive feature is a boolean feature of pronouns or determiners. It tells whether the word is reflexive, i.e. it refers to the subject of its clause.
In Irish, the reflexive pronoun is féin
Examples
- bhí fhios agam cheana féin “I already knew”
- bhí a chiall féin do gach duine ina thaibhreamh féin “Everybody’s own meaning was in his own dream”
Tense
: tense
Tense is a feature that specifies the time when the action took / takes / will take place, in relation to the current moment or to another action in the utterance.
Past
: past tense
The past tense denotes actions that happened before the current moment. In Irish, past tense is indicated in the verb through the addition of lenition and/or a d’- prefix.
Examples
- Bhí a ngruanna faoi lasadh. “Their cheeks were glowing.”
- D’fhan sé ansin inné. “He stayed there yesterday.”
Pres
: present tense
The present tense denotes actions that are happening right now or that habitually happen.
Examples
- Tá sé ina chodladh. “He is asleep.”
- Dathaíonn siad na pictiúir. “They colour in the pictures.”
Fut
: future tense
The future tense denotes actions that will happen after the current moment. In Irish, the future is indicated by the addition of a -f-, or -ó- suffix, with endings depending on person.
- Caithfidh mé sin a fhoghlaim! “I have to learn that!”
- Tosóidh an cheolchoirm ar 8pm. “The concert will start at 8PM.”
VerbForm
: form of verb or deverbative
In Irish, verb form is a feature of words which have the appearance of a verb, although they function as other parts of speech.
This feature appears most commonly as an inifitive
construction, which functions as a noun. This feature also appears as a copula
, a particle
or a verbal noun
.
Inf
: infinitive
The infinitive verb form functions as a noun. The inifitive is always preceded by a particle or a preposition. Following a particle, the verb form takes lenition.
Examples
Introduced by particle
- a dhéanamh “to do”
- a chur “to put”
- a rá “to talk”
Introduced by preposition
- le déanamh “to do”
- chun féachaint “to see”
- á rá “to talk”
Cop
: copula
The copula verb form usually functions as a copula verb, though it can also be used as a mark, to introduce a complement clause, or as the root of the sentence. The copula takes many forms - predominately is, as well as gur, ba, ní, etc. (see cop)
Examples
- Is mise Briain “I am Brian”
-
is é an watt (W) an t-aonad cumhachta “The watt (W) is the unit of power”
- Dá mba mise thú “If I were you”
- Más rud é “if it is a thing”
-
Ar mhaith leat “would you like”
- Sin a bhfuil ann “That is what is there”
- Cén fáth a ndeachaigh sé amach? “For what reason did he go out?”
Part
: participle
The participle verb form functions as an adjective. It can be used to modify the head noun, or to introduce an adjectival predicate complement. (see xcomp:pred) The participle is usually inflected by adding the suffix -te (-the) or -ta (-tha) to the lemma.
Examples
Adjectival modifier
- Gailge briste “broken Irish”
- na ndaoine fásta “the adults” lit. “the grown people”
- Dé Domhnaigh seo caite “this past Sunday”
Introducing complement clause
- Tá gearán déanta ag Unison “Unison have made a complaint”
- An mothaíonn tú sábháilte? “Do you feel safe?”
- Tá a lán scríofa ar an ábhar seo “There’s a lot written on this topic”
Vnoun
: verbal noun
Verbal nouns are nouns that take the form of a verb. They may be used to introduce a clausal complement, (see xcomp), as a conjunct, or as a root of the sentence. The noun is preceded by the preposition ag which loosely translates to “in the process of” in this situation.
Examples
- beidh Máire Andrews ag insint scéalta difriúla “Mary Andrews will be telling different stories”
- bhí Bhreandán ag caitheamh a chuid airgid “Brendan was spending his money”
- Bhí Éamonn ag obair go lánaimsireach “Eamon was working full-time”
Voice
: voice
The Irish autonomous voice is similar to the passive construction, in that the agent of the verb is not (necessarily) specified. However, in this constuction, the object remains in accusative case, as opposed to the nominative case used in the passive voice. The subject in this construction remains anonymous, as a dummy subject.
Auto
: autonomous voice
The autonomous voice is formed with a different verb ending: -t(e)ar in the present tense, -(e)adh in the past tense, -f(e)ar, in the future tense, and -f(a)í in the conditional.
Examples
- Tugadh an bhreith “the verdict was given”
- rugadh iníon óg rua d’Eithne “a young redheaded daughter was born to Eithne”


Elixir v1.3.4 Path
This module provides conveniences for manipulating or retrieving file system paths.
The functions in this module may receive a chardata as argument (i.e. a string or a list of characters / string) and will always return a string (encoded in UTF-8).
The majority of the functions in this module do not
interact with the file system, except for a few functions
that require it (like wildcard/2
and expand/1
.
Summary
Functions
Converts the given path to an absolute one. Unlike
expand/1
, no attempt is made to resolve ..
, .
or ~
Builds a path from relative_to
to path
. If path
is already
an absolute path, relative_to
is ignored. See also relative_to/2
Returns the last component of the path or the path itself if it does not contain any directory separators
Returns the last component of path
with the extension
stripped. This function should be used to remove a specific
extension which may, or may not, be there
Returns the directory component of path
Converts the path to an absolute one and expands
any .
and ..
characters and a leading ~
Expands the path relative to the path given as the second argument
expanding any .
and ..
characters. If the path is already an
absolute path, relative_to
is ignored
Returns the extension of the last component of path
Joins a list of strings
Joins two paths
Forces the path to be a relative path
Returns the given path
relative to the given from
path.
In other words, it tries to strip the from
prefix from path
Convenience to get the path relative to the current working directory. If, for some reason, the current working directory cannot be retrieved, returns the full path
Returns the path
with the extension
stripped
Returns the path
with the extension
stripped. This function should be used to
remove a specific extension which might, or might not, be there
Splits the path into a list at the path separator
Returns the path type
Traverses paths according to the given glob
expression, and returns a
list of matches
Types
Functions
Converts the given path to an absolute one. Unlike
expand/1
, no attempt is made to resolve ..
, .
or ~
.
Unix examples
Path.absname("foo")
#=> "/usr/local/foo"
Path.absname("../x")
#=> "/usr/local/../x"
Windows
Path.absname("foo").
"D:/usr/local/foo"
Path.absname("../x").
"D:/usr/local/../x"
Builds a path from relative_to
to path
. If path
is already
an absolute path, relative_to
is ignored. See also relative_to/2
.
Unlike expand/2
, no attempt is made to
resolve ..
, .
or ~
.
Examples
iex> Path.absname("foo", "bar")
"bar/foo"
iex> Path.absname("../x", "bar")
"bar/../x"
Returns the last component of the path or the path itself if it does not contain any directory separators.
Examples
iex> Path.basename("foo")
"foo"
iex> Path.basename("foo/bar")
"bar"
iex> Path.basename("/")
""
Returns the last component of path
with the extension
stripped. This function should be used to remove a specific
extension which may, or may not, be there.
Examples
iex> Path.basename("~/foo/bar.ex", ".ex")
"bar"
iex> Path.basename("~/foo/bar.exs", ".ex")
"bar.exs"
iex> Path.basename("~/foo/bar.old.ex", ".ex")
"bar.old"
Returns the directory component of path
.
Examples
iex> Path.dirname("/foo/bar.ex")
"/foo"
iex> Path.dirname("/foo/bar/baz.ex")
"/foo/bar"
Converts the path to an absolute one and expands
any .
and ..
characters and a leading ~
.
Examples
Path.expand("/foo/bar/../bar")
#=> "/foo/bar"
Expands the path relative to the path given as the second argument
expanding any .
and ..
characters. If the path is already an
absolute path, relative_to
is ignored.
Note, that this function treats path
with a leading ~
as
an absolute one.
The second argument is first expanded to an absolute path.
Examples
# Assuming that the absolute path to baz is /quux/baz
Path.expand("foo/bar/../bar", "baz")
#=> "/quux/baz/foo/bar"
Path.expand("foo/bar/../bar", "/baz")
"/baz/foo/bar"
Path.expand("/foo/bar/../bar", "/baz")
"/foo/bar"
Returns the extension of the last component of path
.
Examples
iex> Path.extname("foo.erl")
".erl"
iex> Path.extname("~/foo/bar")
""
Joins a list of strings.
This function should be used to convert a list of strings to a path. Note that any trailing slash is removed on join.
Examples
iex> Path.join(["~", "foo"])
"~/foo"
iex> Path.join(["foo"])
"foo"
iex> Path.join(["/", "foo", "bar/"])
"/foo/bar"
Joins two paths.
The right path will always be expanded to its relative format and any trailing slash is removed on join.
Examples
iex> Path.join("foo", "bar")
"foo/bar"
Forces the path to be a relative path.
Unix examples
Path.relative("/usr/local/bin") #=> "usr/local/bin"
Path.relative("usr/local/bin") #=> "usr/local/bin"
Path.relative("../usr/local/bin") #=> "../usr/local/bin"
Windows examples
Path.relative("D:/usr/local/bin") #=> "usr/local/bin"
Path.relative("usr/local/bin") #=> "usr/local/bin"
Path.relative("D:bar.ex") #=> "bar.ex"
Path.relative("/bar/foo.ex") #=> "bar/foo.ex"
Returns the given path
relative to the given from
path.
In other words, it tries to strip the from
prefix from path
.
This function does not query the file system, so it assumes no symlinks between the paths.
In case a direct relative path cannot be found, it returns the original path.
Examples
iex> Path.relative_to("/usr/local/foo", "/usr/local")
"foo"
iex> Path.relative_to("/usr/local/foo", "/")
"usr/local/foo"
iex> Path.relative_to("/usr/local/foo", "/etc")
"/usr/local/foo"
Convenience to get the path relative to the current working directory. If, for some reason, the current working directory cannot be retrieved, returns the full path.
Returns the path
with the extension
stripped.
Examples
iex> Path.rootname("/foo/bar")
"/foo/bar"
iex> Path.rootname("/foo/bar.ex")
"/foo/bar"
Returns the path
with the extension
stripped. This function should be used to
remove a specific extension which might, or might not, be there.
Examples
iex> Path.rootname("/foo/bar.erl", ".erl")
"/foo/bar"
iex> Path.rootname("/foo/bar.erl", ".ex")
"/foo/bar.erl"
Splits the path into a list at the path separator.
If an empty string is given, returns an empty list.
On Windows, path is split on both “\” and “/“ separators and the driver letter, if there is one, is always returned in lowercase.
Examples
iex> Path.split("")
[]
iex> Path.split("foo")
["foo"]
iex> Path.split("/foo/bar")
["/", "foo", "bar"]
Returns the path type.
Unix examples
Path.type("/") #=> :absolute
Path.type("/usr/local/bin") #=> :absolute
Path.type("usr/local/bin") #=> :relative
Path.type("../usr/local/bin") #=> :relative
Path.type("~/file") #=> :relative
Windows examples
Path.type("D:/usr/local/bin") #=> :absolute
Path.type("usr/local/bin") #=> :relative
Path.type("D:bar.ex") #=> :volumerelative
Path.type("/bar/foo.ex") #=> :volumerelative
Traverses paths according to the given glob
expression, and returns a
list of matches.
The wildcard looks like an ordinary path, except that certain “wildcard characters” are interpreted in a special way. The following characters are special:
?
- matches one character*
- matches any number of characters up to the end of the filename, the next dot, or the next slash**
- two adjacent*
’s used as a single pattern will match all files and zero or more directories and subdirectories[char1,char2,...]
- matches any of the characters listed; two characters separated by a hyphen will match a range of characters. Do not add spaces before and after the comma as it would then match paths containing the space character itself.{item1,item2,...}
- matches one of the alternatives Do not add spaces before and after the comma as it would then match paths containing the space character itself.
Other characters represent themselves. Only paths that have exactly the same character in the same position will match. Note that matching is case-sensitive; i.e. “a” will not match “A”.
By default, the patterns *
and ?
do not match files starting
with a dot .
unless match_dot: true
is given in opts
.
Examples
Imagine you have a directory called projects
with three Elixir projects
inside of it: elixir
, ex_doc
and dynamo
. You can find all .beam
files
inside the ebin
directory of each project as follows:
Path.wildcard("projects/*/ebin/**/*.beam")
If you want to search for both .beam
and .app
files, you could do:
Path.wildcard("projects/*/ebin/**/*.{beam,app}")