You can use boolean logic (e.g. AND/OR/NOT) for complex search queries. For more help and examples, see the search documentation.
Search by package name:
my-package (implicit)
name:my-package (explicit)
Search by package filename:
filename:my-package.ext
Search by package tag:
tag:latest
Search by package version:
version:1.0.0
prerelease:true (prereleases)
prerelease:false (no prereleases)
Search by package architecture:
architecture:x86_64
Search by package distribution:
distribution:el
Search by package license:
license:MIT
Search by package format:
format:deb
Search by package status:
status:in_progress
Search by package file checksum:
checksum:5afba
Search by package security status:
severity:critical
Search by package vulnerabilities:
vulnerabilities:>1
vulnerabilities:<1000
Search by # of package downloads:
downloads:>8
downloads:<100
Search by package type:
type:binary
type:source
Search by package size (bytes):
size:>50000
size:<10000
Search by dependency name/version:
dependency:log4j
dependency:log4j=1.0.0
dependency:log4j>1.0.0
Search by uploaded date:
uploaded:>"1 day ago"
uploaded:<"August 14, 2022 EST"
Search by entitlement token (identifier):
entitlement:3lKPVJPosCsY
Search by policy violation:
policy_violated:true
deny_policy_violated:true
license_policy_violated:true
vulnerability_policy_violated:true
Search by repository:
repository:repo-name
Search by last download date:
last_downloaded:<"30 days ago"
last_downloaded:>"August 14, 2022 EST"
Search queries for all Debian-specific (and related) package types
Search by component:
deb_component:unstable
Search queries for all Maven-specific (and related) package types
Search by group ID:
maven_group_id:org.apache
Search queries for all Docker-specific (and related) package types
Search by image digest:
docker_image_digest:sha256:7c5..6d4
(full hashref only)
Search by layer digest:
docker_layer_digest:sha256:4c4..ae4
(full hashref only)
Search queries for all Generic-specific package types
Search by file path:
generic_filepath:path/to/file.txt
Search by directory:
generic_directory:path/to
Field type modifiers (depending on the type, you can influence behaviour)
For all queries, you can use:
~foo for negation
For string queries, you can use:
^foo to anchor to start of term
foo$ to anchor to end of term
foo*bar for fuzzy matching
For number/date or version queries, you can use:
>foo for values greater than
>=foo for values greater / equal
<foo for values less than
<=foo for values less / equal
Need a secure and centralised artifact repository to deliver Alpine,
Cargo,
CocoaPods,
Composer,
Conan,
Conda,
CRAN,
Dart,
Debian,
Docker,
Generic,
Go,
Helm,
Hex,
HuggingFace,
LuaRocks,
Maven,
MCP,
npm,
NuGet,
P2,
Python,
RedHat,
Ruby,
Swift,
Terraform,
Vagrant,
VSX,
Raw & More packages?
Cloudsmith is the new standard in Package / Artifact Management and Software Distribution.
With support for all major package formats, you can trust us to manage your software supply chain.
busy
3.2.0
One-liner (summary)
Description
Busy
Busy is a personal time management tool, designed to help us all through our crazy busy days with as little stress as possible. It's simple, fast, and fun to use.
Usage
Principles
Busy is built with the following usage principles in mind:
- Monotasking: We each focus better when we work on exactly one task at a time. So busy only shows you one task.
- Keyboard-driven: Productive people use the keyboard effectively, because muscle memory builds up over time, and it's faster to hit a key than to find an icon on a screen and move the pointer.
- Offline use: It's designed to run on your laptop or desktop computer, without needing an internet connection, so it works extremely fast under any conditions.
- Multi-platform Because Busy is a terminal-based application, it will run on MacOS, Linux, or Windows.
- Personal: Busy is not a collaboration platform or project management application. It's for managing your personal time, not assigning things to others.
- Importance over Urgency: Stop stressing out over last-minute tasks and impending deadlines! Busy makes it easy to capture future tasks and remember to do them early enough to reduce the pressure.
- Editable data: The data is stored in text files, which can easily be edited outside of Busy itself. (In fact, Busy started as a todo.txt type of approach and grew from there.)
_The idea of Importance over Urgency comes from the book "The 7 Habits of Highly Effective People". Although we firmly disagree with Steven Covey's statements on gay rights, the book contains excellent ideas._
Installation
You'll need a terminal emulator to access a Bash-type prompt. Examples include:
- iTerm2 or Terminal on MacOS
- Gnome Terminal or XTerm on Linux
- Bash On Ubunto on Windows
- Terminator on all platforms
Busy also requires Python 3.6.5 or later. To check whether you already have the right version of Python on your system, start your terminal emulator and type:
` python -V `
If that doesn't work, try:
` python3 -V `
If you don't have Python, or your version is out of date, install or upgrade it. In most cases, you'll want to do so using your system's package manager (such as Homebrew on MacOS or APT on Linux). If you're not familiar with package managers, then download Python from [the Python.org site](https://www.python.org/downloads/) directly and follow the instructions provided there. When done, use the version check above to confirm it's installed and the version is 3.6.5 or greater.
Python comes with PIP, which enables installation of Python packages from a central server called PyPI.
From now on, we're going to use python3 and pip3 in code snippets, although your system might prefer simply python or pip. Just edit them.
Here's the command to install the latest stable version of Busy itself:
` sudo pip3 install busy && pip3 show busy `
If you have previously installed Busy, and want to upgrade to the latest version, type:
` sudo pip3 install --upgrade busy && pip3 show busy `
Overview
Busy ships with 2 user interfaces, both of them terminal-based and keyboard-driven:
- Shell UI - A command-line interface (CLI) using shell conventions and called directly from the shell, one command at a time.
- Curses UI - A faster, more visual interface with one-key commands that remains visible the entire time it's being used.
Some commands also use your favorite terminal-based text editor, such as Emacs, vi, or Nano. It's possible to use Busy without a text editor, but functionality is limited.
Busy's core model is a collection of Items, the most interesting of which are Tasks. Items are organized into Queues, which are ordered sets. You work on the top Task in the Queue, and when it's done, that Task gets removed from the Queue to reveal the next one. There is a default Queue (called "tasks") but you can also create other Queues, for example a shopping list or discussion list.
In addition to the "tasks" Queue, Busy maintains the "plans" Queue for future tasks (don't worry about them yet!) and the "done" Queue as a record of what's been completed in the past.
Using the Shell UI
To get started, add some Tasks to your default Queue.
` busy add "Take a shower" busy add "Do the laundry" busy add "Phone mom" busy add "Donate to the Busy project" `
Then, when you're ready to start your day, ask Busy what to do first:
` busy top `
Returns:
` Take a shower `
_Yes, Busy is great for tracking daily, personal, habitual tasks in addition to work tasks. It feels great to mark things as done!_
When you've finished that task, mark it off to find the next task.
` busy finish `
It will ask you to confirm that you're done. Then request the next task:
` busy top `
Which will tell you what to do next:
` Do the laundry `
If you want to see the whole Queue, with sequence numbers, type:
` busy list `
Here's the list you will see. Note that the completed Task is gone:
` 1 Do the laundry 2 Phone mom 3 Donate to the Busy project `
If you decide, in the moment, to wait until later today to perform a task, drop it to the bottom of the Queue using the drop command:
` busy drop `
Then busy list will return:
` 1 Phone mom 2 Donate to the Busy project 3 Do the laundry `
If you see a task on the list that seems urgent, and you intend to perform it immediately, pop it to the top of the list:
` busy pop 2 `
_Our use of the term "pop" for a command doesn't quite fit with the computing term "pop". It might change in the future._
Then busy get will return:
` Donate to the Busy project `
Let's say you realize that it's not an appropriate task for today, but you want to defer it to tomorrow:
` busy defer `
It will ask you to confirm "tomorrow" as the day for deferral. Agree with it for now.
At the start of a new day, tell Busy to add all the previously deferred Tasks to the current Queue:
` busy activate `
Commands
Here's a summary of the commands in Busy.
- add adds a new item to the bottom of the queue. The item description may be included after the command or written to stdin (i.e. typed on the next line).
- top gets the top item in the queue, referred to as the "current" item. There are no options.
- list lists the items in the queue in order with their sequence numbers.
- pop moves a task or set of items to the top of a queue.
- drop moves a task or set of items to the bottom of a queue.
- delete permanently removes a task or set of items from a queue.
- edit opens a text editor to edit items - the default is to edit only the top item.
- manage is the same as edit, but defaults to edit the whole queue.
- finish removes a task or tasks from the tasks queue and adds it to the done queue, so it's complete. Good job!
- defer removes a task or set of tasks from the tasks queue and schedules it or them to reappear at a future date in the plans queue.
- activate moves current tasks from the plans queue to the tasks queue. Get to work!
- queues to list all the queues.
- tags to list all the tags.
Except for add and top, commands allow the designation of specific items to be acted upon. Item designation can be performed using sequence numbers or tags.
Sequence numbers
Sequence numbers appear in the output from the list command. Note that the numbering starts with 1, and is not an ID -- the number of a item will change when the queue is modified. So always reference the most recent output from the list command.
To designate more than one item, separate the sequence numbers with a space.
When used to designate items, a range of sequence numbers is separated by a hyphen, with no whitespace, and is inclusive. For example, 4-6 designates items 4, 5, and 6. A hyphen without a number after it includes all the items from that item to the end of the queue. A hyphen on its own indicates the last item in the queue.
Below are some examples of task designations by sequence number.
- busy pop 5 pops item number 5
- busy drop 3-7 drops items 3 through 7 (4 items)
- busy list 3- lists all the items from number 3 through the end of the list
- busy delete 3 5 7 9 deletes only the items designated
- busy defer - defers the last task
- busy edit -4 is an error! Use busy edit 1-4 instead
- busy manage allows you to edit the entire queue
Items will always be handled in the order they appear in the queue, regardless of the order the criteria are provided. So for example, if a pop command designates some items, they will be moved to the top of the queue in the order, relative to each other, they currently appear in the queue.
The sequence numbers in the list command output are from the queue itself. So the list command does not modify the sequence numbers, even when item designation is applied.
Tags
Items can have tags, which are space-separated hashtags in the item description. An item can have no tags, one tag, or more than one tag. For example the following item description has the tag "errands":
` go to the supermarket #errands `
Tags cannot contain punctuation.
Hash tags may be used for item designation, in which case the hash itself ("#") is omitted from the command line. For example, the following command will move all the items with the #errands tag to the top of the queue.
` busy pop errands `
Whitespace-separated item designation criteria are additive -- that is, a logical OR. For example, the following command will delete all the admin tasks, sales tasks, and tasks 3 and 4.
` busy delete admin sales 3 4 `
Default item designations
For the most part, commands that accept item designations default to only act on the top item in the queue. The exceptions are:
- list defaults to list the entire queue
- pop defaults to pop the last item in the queue to the top
- activate defaults to activate items for today (more on that below)
Alternate queues
Busy will manage any number of queues, which are entirely separate ordered sets of items. For example, you might have a shopping queue for items to buy at the store, and a movies queue for films you'd like to watch. The default queue is called tasks and has special properties related to planning.
To designate an alternate queue, use the --queue option on a command. For example:
` busy add "Skimmed Milk" --queue shopping busy top --queue movies `
Managing plans
The default tasks queue supports several specific commands related to planning -- that is, scheduling tasks for the future. They are finish, defer, and activate. The task-specific commands do not accept a --queue modifier, because they only work on the default tasks queue. Planned tasks are kept in another special queue called plans, and completed tasks are kept in a queue called done.
The task commands accept item designations. The defer and finish commands reference the tasks queue; the activate command references the plans queue. The default for defer and finish is the top item in the tasks queue; the default for activate is to activate only plans deferred to today or earlier.
Planning by date
Planning is by date, not time, and is relative to the current date according to the system clock.
In the defer command, the date can be specified using the --to or --for option (they are interchangable). If the options are omitted, then the date can be provided as input.
The date may take any of the following forms:
- A specific date in YYYY-MM-DD format, such as 2018-10-28. Slashes are also acceptable, but the order is always year, then month, then day.
- A specific date without the year in MM-DD format, such as 7-4, which will defer the item to that date in the future (even if it's in the next year).
- A specific day of the month as a simple integer, such as 12, which will defer the item to that day of the month, in either the current month or the next month.
- An integer, a space, and the word day or days, such as 4 days, which will defer the item to that number of days fr
| Status | Completed |
|---|---|
| Checksum (MD5) | 0628e60e98e71fbbf1cdee3e67a0cda2 |
| Checksum (SHA-1) | 0ecf141eab90e831da21d71b497084dcc660b6f2 |
| Checksum (SHA-256) | 802c38c54e4f6085ca193b393042d714279979a6e391adcafa1f5a78bf5b8435 |
| Checksum (SHA-512) | 951dc81cb32bbbbed86cdfeb3c908e97cb5281284842a6b38ac4cd19ecbb17bf69… |
| GPG Signature | |
| GPG Fingerprint | 6811684bac0b8895434e97bdd4391b8fb999e537 |
| Storage Region | Dublin, Ireland |
| Type | Binary (contains binaries and binary artifacts) |
| Uploaded At | 4 months, 3 weeks ago |
| Uploaded By |
|
| Slug Id | busy-320-py3-none-anywhl-oqi7 |
| Unique Id | CiYZi1Z08cEbbLxB |
| Version (Raw) | 3.2.0 |
| Version (Parsed) |
|
| extended metadata | |
| Author | Francis Potter <busy@fpotter.com> |
| Homepage URL | http://gitlab.com/fpotter/tools/busy |
| Metadata Version | 2.1 |
| Py Filetype | bdist_wheel |
| Py Version | py3 |
| pkg | busy-3.2.0-py3-none-any.whl |
5
52.2 KB |
md5 | sha1 | sha256 | sha512 |
This package has 94 files/directories.
Last scanned
4 months, 3 weeks ago
Scan result
Clean
Vulnerability count
0
Max. severity
UnknownPackage statistics are no longer available on cloudsmith.io. Please visit our new web app to access this feature.
You can embed a badge in another website that shows this or the latest version of this package.
To embed the badge for this specific package version, use the following:
[](https://cloudsmith.io/~demo-docs/repos/awesome-repo/packages/detail/python/busy/3.2.0/a=noarch;xf=bdist_wheel;xn=busy;xv=py3/)
|This version of 'busy' @ Cloudsmith|
.. |This version of 'busy' @ Cloudsmith| image:: https://api.cloudsmith.com/v1/badges/version/demo-docs/awesome-repo/python/busy/3.2.0/a=noarch;xf=bdist_wheel;xn=busy;xv=py3/?render=true
:target: https://cloudsmith.io/~demo-docs/repos/awesome-repo/packages/detail/python/busy/3.2.0/a=noarch;xf=bdist_wheel;xn=busy;xv=py3/
image::https://api.cloudsmith.com/v1/badges/version/demo-docs/awesome-repo/python/busy/3.2.0/a=noarch;xf=bdist_wheel;xn=busy;xv=py3/?render=true[link="https://cloudsmith.io/~demo-docs/repos/awesome-repo/packages/detail/python/busy/3.2.0/a=noarch;xf=bdist_wheel;xn=busy;xv=py3/",title="This version of 'busy' @ Cloudsmith"]
<a href="https://cloudsmith.io/~demo-docs/repos/awesome-repo/packages/detail/python/busy/3.2.0/a=noarch;xf=bdist_wheel;xn=busy;xv=py3/"><img src="https://api.cloudsmith.com/v1/badges/version/demo-docs/awesome-repo/python/busy/3.2.0/a=noarch;xf=bdist_wheel;xn=busy;xv=py3/?render=true" alt="This version of 'busy' @ Cloudsmith" /></a>
rendered as:
To embed the badge for the latest package version, use the following:
[](https://cloudsmith.io/~demo-docs/repos/awesome-repo/packages/detail/python/busy/latest/a=noarch;xf=bdist_wheel;xn=busy;xv=py3/)
|Latest version of 'busy' @ Cloudsmith|
.. |Latest version of 'busy' @ Cloudsmith| image:: https://api.cloudsmith.com/v1/badges/version/demo-docs/awesome-repo/python/busy/latest/a=noarch;xf=bdist_wheel;xn=busy;xv=py3/?render=true&show_latest=true
:target: https://cloudsmith.io/~demo-docs/repos/awesome-repo/packages/detail/python/busy/latest/a=noarch;xf=bdist_wheel;xn=busy;xv=py3/
image::https://api.cloudsmith.com/v1/badges/version/demo-docs/awesome-repo/python/busy/latest/a=noarch;xf=bdist_wheel;xn=busy;xv=py3/?render=true&show_latest=true[link="https://cloudsmith.io/~demo-docs/repos/awesome-repo/packages/detail/python/busy/latest/a=noarch;xf=bdist_wheel;xn=busy;xv=py3/",title="Latest version of 'busy' @ Cloudsmith"]
<a href="https://cloudsmith.io/~demo-docs/repos/awesome-repo/packages/detail/python/busy/latest/a=noarch;xf=bdist_wheel;xn=busy;xv=py3/"><img src="https://api.cloudsmith.com/v1/badges/version/demo-docs/awesome-repo/python/busy/latest/a=noarch;xf=bdist_wheel;xn=busy;xv=py3/?render=true&show_latest=true" alt="Latest version of 'busy' @ Cloudsmith" /></a>
rendered as:
These instructions assume you have setup the repository first (or read it).
To install/use busy @ version 3.2.0 ...
pip install 'busy==3.2.0'
You can also install the latest version of this package:
pip install --upgrade 'busy'
If necessary, you can specify the repository directly:
pip install \
--index-url=https://dl.cloudsmith.io/public/demo-docs/awesome-repo/python/simple/ \
busy==3.2.0
If you've got a project requirements.txt file, you can specify this as a dependency:
--index-url=https://dl.cloudsmith.io/public/demo-docs/awesome-repo/python/simple/
busy==3.2.0
In addition, you can use this repository as an extra index url. However, please read our documentation on this parameter before using it. For example in a requirements.txt file:
--extra-index-url=https://dl.cloudsmith.io/public/demo-docs/awesome-repo/python/simple/
busy==3.2.0