Changes between Version 3 and Version 4 of ProjectCommands


Ignore:
Timestamp:
Jun 3, 2019, 4:26:39 PM (5 years ago)
Author:
Mikael Brandström Durling
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ProjectCommands

    v3 v4  
    11= Project commands =
     2
     3Most work should be done as part of a registered project. Without selecting a project before (or at) submission of queue jobs, the jobs will end up in a low priority queue.
    24
    35== Enter project ==
    46This has to be done before you can work within a project.
    57
    6 ==== Usage: ```proj [-c] [project-name]```  ====
    7 If project name is omitted, change to the default project as set by ```selectproject```.
     8==== Usage: `proj [-c] [project-name]`  ====
     9If project name is omitted, change to the default project as set by `selectproject`.
     10
     11The  `-c` option makes the command change directory into the project folder. (Saves you a `cd /proj/....` command).
    812
    913
     
    1115This will set the default project used by ```proj```. Setting a default project will save you some typing if you are always switching to the same project.
    1216
    13 ==== Usage: ```selectproj <project-name> ``` ====
     17==== Usage: `selectproj <project-name> `====
    1418
    1519== List your projects ==
    1620List all projects you are registered with. It will also give your current quota and disk usage for the projects.
    1721
    18 ==== Usage: ```listproj [-q]``` ====
     22==== Usage: `listproj [-q]` ====
    1923
    20 If ```-q``` is given, it will only list projects that are using 90% or more of the allocated disk space.
     24If `-q` is given, it will only list projects that are using 90% or more of the allocated disk space.
    2125
    2226