A comprehensive self-management System
Home Page: https://smos.online
License: MIT License
See the online version to try it out and see the documentation site for more information.
Smos is free and open-source software. Building it takes time, energy and money. Please consider supporting the project at https://docs.smos.online/support
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot]")
Step to reproduce:
smosrnresult...
The image is cropped on the right side. This is the result despite having a wide enough monitor to fit more information.
Possible solution:
simple:
Have the truncation be based on a percentage of total width of the screen, but always truncating only from the left (start of the filepath) and never truncating from the right (end of the filepath that typically includes the final filename)
complex:
Have the full path show in a limited width by rotating text, like web-banners from the 90's 😛 (only half joking)
It would be nice to be able to undo this, so the file browser cursor may have to keep its own undo stack.
Have:
# ~/.config/nixpkgs/home.nix
{
imports = [
../program/smos
];
}
and
# ~/.config/nixpkgs/program/smos/default.nix
{ pkgs, lib, ... }:
with lib;
let
smosModule = (builtins.fetchGit {
url = "https://github.com/NorfairKing/smos";
ref = "master";
rev = "53e1f37a06f16f2b32452ba0cc736e3707eb268a"; # Add a recent version here.
} + "/nix/program.nix");
in
{
imports = [
smosModule
# [...]
];
smos = {
enable = true;
backup = {
enable = true;
};
sync = {
enable = false;
username = "YOURUSERNAMEHERE";
password = "YOURPASSWORDHERE";
};
};
}
Getting
error: The option
smos' defined in~/.config/nixpkgs/program/smos' does not exist.
The smos-query reports should offer a way to discover available
pre-configured reports.
Something like:
$ smos-query report --list
Currently any deadline fewer than 7 days into the future will appear. Someone might want to make this more or less.
Hi,
I'm failing to build smos with the stack file included:
$ stack install :smos
Cloning f67e8da673b3f934518810d9681206ff8cf1bf5e from https://github.com/NorfairKing/cursor.git
Mismatched package metadata for Repo from https://github.com/NorfairKing/cursor.git, commit f67e8da673b3f934518810d9681206ff8cf1bf5e in subdir cursor
Found: cursor-0.0.0.1 with cabal file 25a2c9fe64940f7d21b76656c09ec168671ec378ff0b74297c40070b268596c8,1509 and tree 30c3e53fce854471c5de7a5ef0fa545a1ca194812697c2675db05b31da26bb37,1760
Expected: name == cursor, version == 0.0.0.1, tree == 30c3e53fce854471c5de7a5ef0fa545a1ca194812697c2675db05b31da26bb37,1760, cabal file == ae998725ceeebfc356f78e16ecb3c6683c4b318aa6481f9ed8edab2419a1f2cf,1509
It looks like something is wrong with the dependencies.
This is on Ubuntu 18.04 with stack 2.1.3
$ stack --version
Version 2.1.3, Git revision 636e3a759d51127df2b62f90772def126cdf6d1f (7735 commits) x86_64 hpack-0.31.2
Result: Nothing happens in the 2nd smos instance
Expected: An error message is shown indicating that the file is already open?
Steps to reproduce the problem:
You will notice that the cursor disappears (because it jumped up), but the viewbox doesn't change.
The viewbox does jump when you create a header ('h'), but not when you navigate using 'gg', 'G', 'j', 'k'.
Hitting q in the help search line exits the help screen.
It should behave differently. since it's currently impossible to
search for a query related command, if any.
Something like gg for top of the file browser & G for bottom would make navigation more consistent with the rest of the UI
Windows is currently not supported, mostly because I don't have any windows machines but I'm not opposed to it.
Let's start with something basic that looks the same as the non-interactive agenda report:
So that's a scrollable list of entries that have:
Then we want to be able to press 'enter' to jump to that header.
ATM, a template such as:
- entry: Example template %F
forest:
- Subdir %y
Run with smos-scheduler like:
$ smos-scheduler --workflow-dir `pwd` --config-file example-config.yaml --state-file example-state.yaml
Results in a file like:
- entry: Example template 2019-12-22
forest:
- Subdir 19
Instead, it would be better to put those new entries in the TODO state.
The .smos file produced by smos-scheduler would then look like:
- entry:
header: Example template 2019-12-22
state-history:
- state: TODO
time: 2019-12-22 22:00:08.135470693000
forest:
- header: Subdir 19
state-history:
- state: TODO
time: 2019-12-22 22:00:10.296044116000
Creating custom properties is not possible yet.
There is still some code missing.
React to this issue with 👍 If you need this, so I'll add it.
Even while idling, I've seen up to 30% cpu usage, for unknown reasons.
I've installed smos and can open it. I just don't know what to do from here. I'm an org-mode user and interested in learning more about how to use smos. Is there a list of default commands and keybindings? Many thanks in advance.
I get the below error when I try to run stack install :smos on ubuntu. Any suggestions?
[21 of 36] Compiling Graphics.Vty.Input.Loop ( src/Graphics/Vty/Input/Loop.hs, .stack-work/dist/x86_64-linux/Cabal-2.2.0.1/build/Graphics/Vty/Input/Loop.o )
<command line>: can't load .so/.DLL for: libtinfo.so (libtinfo.so: cannot open shared object file: No such file or directory)
I also tried to run it in a nix-shell, but get the below error when nix-shell is trying to start.
evaluating file '/home/hackeryarn/dev/smos/nix/overlay.nix'
error: Please be informed that this pseudo-package is not the only part of
Nixpkgs that fails to evaluate. You should not evaluate entire Nixpkgs
without some special measures to handle failing packages, like those taken
by Hydra.
Essentially the same as https://github.com/NorfairKing/intray/issues/6
smos-sync-client ends up saving the __cfduid cookie instead of the JWT-Cookie:
$ cat .smos/sync-session.dat
__cfduid=REDACTED; Path=/; Expires=Tue, 19-May-2020 11:19:28 GMT; Domain=.REDACTED.com; HttpOnly; Secure
Switching cloudflare off, logging the sync client in via http, and then re-enabling cloudflare lets us circumvent this, but then credentials are sent over http.
When clocking out in an entry three levels deep, al the entries on the way up should be un-collapsed so that it's very easy to see which entry got clocked out.
This would be a nice feature to get an overview of how much you are getting done over time. It's just for fun.
When invoked with two arguments, TASK and FILEPATH, a file is created
under workflow with the name derived from the concatenation of
TASK and FILEPATH (lowercased) even if a file named FILEPATH already
exists.
This is an interesting issue because it involves a change to the state.
I'm open to ideas but I think the easiest way to deal with this is to keep a "clipboard" with the copied node/tree.
There is already a tutorial.smos file in the root dir, but this should be expanded to be something like vimtutor.
Currently all colours are fixed, and they may not be equally readable on all systems, so it would be nice if they were configurable via the config file.
This would also allow for colour themes.
I was testing some aliases/functions I wrote and I can't seem to get smos-archive to work with my custom workflow dir ~/.tasks:
$ cd ~
$ smos-archive .tasks/test.smos
The smos file
/home/prikhi/.tasks/test.smos
is not in the smos workflow directory
/home/prikhi/workflow/
$ grep 'workflow-dir' .config/smos/config.yaml --context=1
workflow-dir:
"/home/prikhi/.tasks"
$ smos-archive .tasks/test.smos --config-file .config/smos/config.yaml
The smos file
/home/prikhi/.tasks/test.smos
is not in the smos workflow directory
/home/prikhi/workflow/
$ smos-archive .tasks/test.smos --workflow-dir ~/.tasks/
The smos file
/home/prikhi/.tasks/test.smos
is not in the smos workflow directory
/home/prikhi/workflow/
Am I doing or setting something incorrectly or is this a bug in smos-archive?
There is no visual indication of where my cursor is in normal mode, so my current workflow is to move the cursor, then press a<esc> to see if the cursor is where I believe it is (there is a cursor in insert mode). This is a bit annoying, and I would hate for that habit spread into other vi-like software.
From comments on #39:
I usually have a smos TUI open 24/7. I also have systemd services & timers for running the sync-client every 10 minutes.
However, if the sync client pulls any updates to an open file, I need to close & re-open the TUI to show these changes. I'm also unsure what would happen if the sync-client updated a file and then I made changes & wrote to a file that was open before the sync-client was run(data-loss I'm assuming?).
I have used the fsnotify library for writing file-watching build scripts, and it could probably be used to address this issue. We could watch for changes to the file that is currently open, but it might be difficult to differentiate between changes from the sync-client & changes from the TUI.
Perhaps we could have every TUI instance watch the sync-metadata.sqlite3 file instead, and reload their current files when we detect the sync database has been modified?
Hey,
I just wanted to try what smos is and did:
git clone https://github.com/NorfairKing/smos
and
nix-build -A smos-static nix/release.nix
this built quite a long time and then failed with
[12 of 12] Compiling Smos.Cursor.SmosFile ( src/Smos/Cursor/SmosFile.hs, dist/build/Smos/Cursor/SmosFile.o )
src/Smos/Cursor/SmosFile.hs:43:1: error: [-Wunused-imports, -Werror=unused-imports]
The import of ‘Control.Monad’ is redundant
except perhaps to import instances from ‘Control.Monad’
To import instances alone, use: import Control.Monad()
|
43 | import Control.Monad
| ^^^^^^^^^^^^^^^^^^^^
builder for '/nix/store/dsd9g8c02y3xr0al2qsqz3rfgqybr7bd-smos-cursor-0.0.0.0.drv' failed with exit code 1
I just wanted to drop this here. Maybe it helps you.
Cheers!
After hitting tab the edit behave in a confused way. You can view with your own eyes at
https://asciinema.org/a/URMJ8AsswGK1ztaLloCg65R20
Something like e for creating a new file at the current hierarchy level & E for creating a new file under the currently selected directory?
Maybe a workflow would be creating a blank line, adding the .smos file extension to it, and then moving the input cursor to the beginning of the line so we can simply type the desired file name?
Show an error if a file with the given name already exists?
Somehow, deleting the contents, when they are empty, doesn't work anymore.
Based on #39
New to smos, I want to give it a try.
I found installation instructions at https://smos.cs-syd.eu/building-installation.html
Cloning is no problem. Building fails. Here is my log:
D:\git>git clone https://github.com/NorfairKing/smos
Cloning into 'smos'...
remote: Enumerating objects: 217, done.
remote: Counting objects: 100% (217/217), done.
remote: Compressing objects: 100% (118/118), done.
remote: Total 12375 (delta 65), reused 152 (delta 41), pack-reused 12158
Receiving objects: 100% (12375/12375), 2.02 MiB | 4.24 MiB/s, done.
Resolving deltas: 100% (7025/7025), done.
D:\git>cd smos
D:\git\smos>stack install autoexporter
Specified source-dir "src/" does not exist
DEPRECATED: The package at Archive from https://github.com/NorfairKing/typed-uuid/archive/5415eaeee9817dfc4846fe4d73efce9312281b27.tar.gz in subdir typed-uuid does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/typed-uuid/archive/5415eaeee9817dfc4846fe4d73efce9312281b27.tar.gz in subdir genvalidity-typed-uuid does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/mergeful/archive/4e3cf189c76d04daf9c26267a64523ec8bb071aa.tar.gz in subdir mergeful does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/mergeful/archive/4e3cf189c76d04daf9c26267a64523ec8bb071aa.tar.gz in subdir genvalidity-mergeful does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/pretty-relative-time/archive/fc62907b36f6f7348d6ae0e97aceb4d41039d57b.tar.gz does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/cursor-fuzzy-time/archive/0b1d393a64b0fd357a9ead86c1ef0d6bd2a4c19f.tar.gz in subdir cursor-fuzzy-time does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/cursor-fuzzy-time/archive/0b1d393a64b0fd357a9ead86c1ef0d6bd2a4c19f.tar.gz in subdir cursor-fuzzy-time-gen does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/fuzzy-time/archive/0c32a1d2e09f1b7421918a845f0b57eceb6752a8.tar.gz in subdir fuzzy-time does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/fuzzy-time/archive/0c32a1d2e09f1b7421918a845f0b57eceb6752a8.tar.gz in subdir fuzzy-time-gen does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/cursor-brick/archive/178d50eac204cdae3d3aeb92c673b18f6245a4cb.tar.gz in subdir cursor-brick does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/cursor/archive/b88cb6f79574fd084f86c322f8e644e10d4cc94e.tar.gz in subdir cursor does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/cursor/archive/b88cb6f79574fd084f86c322f8e644e10d4cc94e.tar.gz in subdir cursor-gen does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/validity/archive/3d7cdbcec808b8249918692adcad187d3cf2e8f4.tar.gz in subdir genvalidity does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/validity/archive/3d7cdbcec808b8249918692adcad187d3cf2e8f4.tar.gz in subdir genvalidity-aeson does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/validity/archive/3d7cdbcec808b8249918692adcad187d3cf2e8f4.tar.gz in subdir genvalidity-bytestring does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/validity/archive/3d7cdbcec808b8249918692adcad187d3cf2e8f4.tar.gz in subdir genvalidity-containers does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/validity/archive/3d7cdbcec808b8249918692adcad187d3cf2e8f4.tar.gz in subdir genvalidity-criterion does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/validity/archive/3d7cdbcec808b8249918692adcad187d3cf2e8f4.tar.gz in subdir genvalidity-hspec does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/validity/archive/3d7cdbcec808b8249918692adcad187d3cf2e8f4.tar.gz in subdir genvalidity-hspec-aeson does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/validity/archive/3d7cdbcec808b8249918692adcad187d3cf2e8f4.tar.gz in subdir genvalidity-hspec-binary does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/validity/archive/3d7cdbcec808b8249918692adcad187d3cf2e8f4.tar.gz in subdir genvalidity-hspec-cereal does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/validity/archive/3d7cdbcec808b8249918692adcad187d3cf2e8f4.tar.gz in subdir genvalidity-hspec-hashable does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/validity/archive/3d7cdbcec808b8249918692adcad187d3cf2e8f4.tar.gz in subdir genvalidity-hspec-optics does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/validity/archive/3d7cdbcec808b8249918692adcad187d3cf2e8f4.tar.gz in subdir genvalidity-path does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/validity/archive/3d7cdbcec808b8249918692adcad187d3cf2e8f4.tar.gz in subdir genvalidity-property does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/validity/archive/3d7cdbcec808b8249918692adcad187d3cf2e8f4.tar.gz in subdir genvalidity-scientific does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/validity/archive/3d7cdbcec808b8249918692adcad187d3cf2e8f4.tar.gz in subdir genvalidity-text does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/validity/archive/3d7cdbcec808b8249918692adcad187d3cf2e8f4.tar.gz in subdir genvalidity-time does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/validity/archive/3d7cdbcec808b8249918692adcad187d3cf2e8f4.tar.gz in subdir genvalidity-unordered-containers does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/validity/archive/3d7cdbcec808b8249918692adcad187d3cf2e8f4.tar.gz in subdir genvalidity-uuid does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/validity/archive/3d7cdbcec808b8249918692adcad187d3cf2e8f4.tar.gz in subdir genvalidity-vector does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/validity/archive/3d7cdbcec808b8249918692adcad187d3cf2e8f4.tar.gz in subdir validity does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/validity/archive/3d7cdbcec808b8249918692adcad187d3cf2e8f4.tar.gz in subdir validity-aeson does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/validity/archive/3d7cdbcec808b8249918692adcad187d3cf2e8f4.tar.gz in subdir validity-bytestring does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/validity/archive/3d7cdbcec808b8249918692adcad187d3cf2e8f4.tar.gz in subdir validity-containers does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/validity/archive/3d7cdbcec808b8249918692adcad187d3cf2e8f4.tar.gz in subdir validity-path does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/validity/archive/3d7cdbcec808b8249918692adcad187d3cf2e8f4.tar.gz in subdir validity-primitive does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/validity/archive/3d7cdbcec808b8249918692adcad187d3cf2e8f4.tar.gz in subdir validity-scientific does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/validity/archive/3d7cdbcec808b8249918692adcad187d3cf2e8f4.tar.gz in subdir validity-text does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/validity/archive/3d7cdbcec808b8249918692adcad187d3cf2e8f4.tar.gz in subdir validity-time does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/validity/archive/3d7cdbcec808b8249918692adcad187d3cf2e8f4.tar.gz in subdir validity-unordered-containers does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/validity/archive/3d7cdbcec808b8249918692adcad187d3cf2e8f4.tar.gz in subdir validity-uuid does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/validity/archive/3d7cdbcec808b8249918692adcad187d3cf2e8f4.tar.gz in subdir validity-vector does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
parsec > using precompiled package
Cabal > using precompiled package
autoexporter> configure
autoexporter> Configuring autoexporter-1.1.15...
autoexporter> build
autoexporter> Preprocessing library for autoexporter-1.1.15..
autoexporter> Building library for autoexporter-1.1.15..
autoexporter> [1 of 2] Compiling Autoexporter
autoexporter>
autoexporter> library\Autoexporter.hs: warning:
autoexporter> Could not specialise imported function `List.isSuffixOf'
autoexporter> Probable fix: add INLINABLE pragma on `List.isSuffixOf'
autoexporter> [2 of 2] Compiling Paths_autoexporter
autoexporter> Preprocessing executable 'autoexporter' for autoexporter-1.1.15..
autoexporter> Building executable 'autoexporter' for autoexporter-1.1.15..
autoexporter> [1 of 2] Compiling Main
autoexporter> [2 of 2] Compiling Paths_autoexporter
autoexporter> Linking .stack-work\dist\e626a42b\build\autoexporter\autoexporter.exe ...
autoexporter>
autoexporter> copy/register
autoexporter> Installing library in C:\sr\snapshots\81a8523c\lib\x86_64-windows-ghc-8.6.5\autoexporter-1.1.15-491tgddMv6A58DbGAbcntl
autoexporter> Installing executable autoexporter in C:\sr\snapshots\81a8523c\bin
autoexporter> Registering library for autoexporter-1.1.15..
Completed 3 action(s).
Copying from C:\sr\snapshots\81a8523c\bin\autoexporter.exe to C:\Users\hjo20125\AppData\Roaming\local\bin\autoexporter.exe
Copied executables to C:\Users\hjo20125\AppData\Roaming\local\bin:
- autoexporter.exe
D:\git\smos>stack install
Specified source-dir "src/" does not exist
DEPRECATED: The package at Archive from https://github.com/NorfairKing/typed-uuid/archive/5415eaeee9817dfc4846fe4d73efce9312281b27.tar.gz in subdir typed-uuid does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/typed-uuid/archive/5415eaeee9817dfc4846fe4d73efce9312281b27.tar.gz in subdir genvalidity-typed-uuid does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/mergeful/archive/4e3cf189c76d04daf9c26267a64523ec8bb071aa.tar.gz in subdir mergeful does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/mergeful/archive/4e3cf189c76d04daf9c26267a64523ec8bb071aa.tar.gz in subdir genvalidity-mergeful does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/pretty-relative-time/archive/fc62907b36f6f7348d6ae0e97aceb4d41039d57b.tar.gz does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/cursor-fuzzy-time/archive/0b1d393a64b0fd357a9ead86c1ef0d6bd2a4c19f.tar.gz in subdir cursor-fuzzy-time does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/cursor-fuzzy-time/archive/0b1d393a64b0fd357a9ead86c1ef0d6bd2a4c19f.tar.gz in subdir cursor-fuzzy-time-gen does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/fuzzy-time/archive/0c32a1d2e09f1b7421918a845f0b57eceb6752a8.tar.gz in subdir fuzzy-time does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/fuzzy-time/archive/0c32a1d2e09f1b7421918a845f0b57eceb6752a8.tar.gz in subdir fuzzy-time-gen does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/cursor-brick/archive/178d50eac204cdae3d3aeb92c673b18f6245a4cb.tar.gz in subdir cursor-brick does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/cursor/archive/b88cb6f79574fd084f86c322f8e644e10d4cc94e.tar.gz in subdir cursor does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/cursor/archive/b88cb6f79574fd084f86c322f8e644e10d4cc94e.tar.gz in subdir cursor-gen does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/validity/archive/3d7cdbcec808b8249918692adcad187d3cf2e8f4.tar.gz in subdir genvalidity does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/validity/archive/3d7cdbcec808b8249918692adcad187d3cf2e8f4.tar.gz in subdir genvalidity-aeson does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/validity/archive/3d7cdbcec808b8249918692adcad187d3cf2e8f4.tar.gz in subdir genvalidity-bytestring does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/validity/archive/3d7cdbcec808b8249918692adcad187d3cf2e8f4.tar.gz in subdir genvalidity-containers does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/validity/archive/3d7cdbcec808b8249918692adcad187d3cf2e8f4.tar.gz in subdir genvalidity-criterion does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/validity/archive/3d7cdbcec808b8249918692adcad187d3cf2e8f4.tar.gz in subdir genvalidity-hspec does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/validity/archive/3d7cdbcec808b8249918692adcad187d3cf2e8f4.tar.gz in subdir genvalidity-hspec-aeson does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/validity/archive/3d7cdbcec808b8249918692adcad187d3cf2e8f4.tar.gz in subdir genvalidity-hspec-binary does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/validity/archive/3d7cdbcec808b8249918692adcad187d3cf2e8f4.tar.gz in subdir genvalidity-hspec-cereal does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/validity/archive/3d7cdbcec808b8249918692adcad187d3cf2e8f4.tar.gz in subdir genvalidity-hspec-hashable does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/validity/archive/3d7cdbcec808b8249918692adcad187d3cf2e8f4.tar.gz in subdir genvalidity-hspec-optics does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/validity/archive/3d7cdbcec808b8249918692adcad187d3cf2e8f4.tar.gz in subdir genvalidity-path does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/validity/archive/3d7cdbcec808b8249918692adcad187d3cf2e8f4.tar.gz in subdir genvalidity-property does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/validity/archive/3d7cdbcec808b8249918692adcad187d3cf2e8f4.tar.gz in subdir genvalidity-scientific does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/validity/archive/3d7cdbcec808b8249918692adcad187d3cf2e8f4.tar.gz in subdir genvalidity-text does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/validity/archive/3d7cdbcec808b8249918692adcad187d3cf2e8f4.tar.gz in subdir genvalidity-time does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/validity/archive/3d7cdbcec808b8249918692adcad187d3cf2e8f4.tar.gz in subdir genvalidity-unordered-containers does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/validity/archive/3d7cdbcec808b8249918692adcad187d3cf2e8f4.tar.gz in subdir genvalidity-uuid does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/validity/archive/3d7cdbcec808b8249918692adcad187d3cf2e8f4.tar.gz in subdir genvalidity-vector does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/validity/archive/3d7cdbcec808b8249918692adcad187d3cf2e8f4.tar.gz in subdir validity does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/validity/archive/3d7cdbcec808b8249918692adcad187d3cf2e8f4.tar.gz in subdir validity-aeson does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/validity/archive/3d7cdbcec808b8249918692adcad187d3cf2e8f4.tar.gz in subdir validity-bytestring does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/validity/archive/3d7cdbcec808b8249918692adcad187d3cf2e8f4.tar.gz in subdir validity-containers does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/validity/archive/3d7cdbcec808b8249918692adcad187d3cf2e8f4.tar.gz in subdir validity-path does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/validity/archive/3d7cdbcec808b8249918692adcad187d3cf2e8f4.tar.gz in subdir validity-primitive does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/validity/archive/3d7cdbcec808b8249918692adcad187d3cf2e8f4.tar.gz in subdir validity-scientific does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/validity/archive/3d7cdbcec808b8249918692adcad187d3cf2e8f4.tar.gz in subdir validity-text does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/validity/archive/3d7cdbcec808b8249918692adcad187d3cf2e8f4.tar.gz in subdir validity-time does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/validity/archive/3d7cdbcec808b8249918692adcad187d3cf2e8f4.tar.gz in subdir validity-unordered-containers does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/validity/archive/3d7cdbcec808b8249918692adcad187d3cf2e8f4.tar.gz in subdir validity-uuid does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
DEPRECATED: The package at Archive from https://github.com/NorfairKing/validity/archive/3d7cdbcec808b8249918692adcad187d3cf2e8f4.tar.gz in subdir validity-vector does not include a cabal file.
Instead, it includes an hpack package.yaml file for generating a cabal file.
This usage is deprecated; please see https://github.com/commercialhaskell/stack/issues/5210.
Support for this workflow will be removed in the future.
Error: While constructing the build plan, the following exceptions were encountered:
In the dependencies for brick-0.47.1(+demos):
unix needed, but the stack configuration has no specified version (latest matching version is 2.7.2.2)
needed due to smos-0.0.0.0 -> brick-0.47.1
In the dependencies for vty-5.25.1:
terminfo must match >=0.3 && <0.5, but the stack configuration has no specified version (latest matching version
is 0.4.1.4)
unix needed, but the stack configuration has no specified version (latest matching version is 2.7.2.2)
needed due to smos-0.0.0.0 -> vty-5.25.1
Some different approaches to resolving this:
* Recommended action: try adding the following to your extra-deps in D:\git\smos\stack.yaml:
- terminfo-0.4.1.4@sha256:64489de75cd4a4a6b427bb870b66274922c851570642e0fd242d320dcb67322b,1658
- unix-2.7.2.2@sha256:e69269a17b9fa26cb77f3f55e86c39d0a4940ccfa0c4bc20826919d2572076ad,3496
Plan construction failed.
D:\git\smos>
We'd also have to be able to undo this.
The smos-sync-client-test fails sometimes because the randomness generates filenames that are too long sometimes.
See https://github.com/NorfairKing/smos/runs/430136367?check_suite_focus=true
It's tempting to just generate smaller paths, but this failure points to a real problem with a sync client sending over files that are too long. We shouldn't let those be added on the sync-server side.
In particular, the sync client fails if the workflow dir doesn't already exist.
From my comments on #39:
It would be great if we had some way to navigate between our non-project and project files from within the smos TUI. I keep a single instance of smos running 24/7 so it was generally easier to keep a large file with all my tasks instead of having to quit smos & re-launch it with a different file.
The way to do this that comes to mind is to have a "file sidebar" that contains the general files & project files in the smos directory. With a naming scheme or nested project directories, we could also render the files in a collapsable tree.
E.g., if we have projects/work_sese_issue-916.smos & projects/work_sese_issue-222.smos(or flip the - & _ or directories like projects/Work/SESE/Issue\ 222 etc), it could be rendered as:
- Work
|- Sese
|- Issue 222
|- Issue 916
With each level being able to collapse it's child items.
We'd want to be able to allow users to disable this functionality. Maybe with a config setting like show-sidebar :: Bool, or defaulting the sidebar to being hidden when smos is started(with an option to change the default visibility).
How do we deal with general & project files that share the same file name? Should we have separate sections for the general & project files? Or show all general files first & then the project files?
Some potential keybindings:
global
sidebar
task list
ctrl-o to jump back from personal.smos to work.smos)The other way we could handle this is with some file-search mechanism similar to the Ctrl-P or fzf vim plugins. I.e., press a keybinding to pop open a list of files & a search input. When text is entered, (fuzzy?) filter the file list, add keybindings for focusing an item in the returned list, and add a binding for switching to the focused file.
This seems to depend on the contents of the smos file. Here's one that triggers the bug on master@048fd646a587e63a7dc201ab48cfee6bb558ba70:
- header: xxx xxxxxxxx xxxxxxxx xxxx xxxxxx
state-history:
- new-state: STARTED
timestamp: 2019-07-03 08:02:42.681757242000+0000
- new-state: TODO
timestamp: 2019-07-03 08:02:42.105753829000+0000
- new-state: TODO
timestamp: 2019-07-03 08:02:41.045923673000+0000
- new-state: STARTED
timestamp: 2019-07-02 17:54:24.734551713000+0000
- new-state: NEXT
timestamp: 2019-07-02 10:52:14.379951466000+0000
- new-state: TODO
timestamp: 2019-07-02 10:52:09.401162609000+0000
tags:
- work
logbook:
- start: 2019-07-03 08:06:05.075234670000+0000
- start: 2019-07-03 07:25:55.901819084000+0000
end: 2019-07-03 08:06:05.075234670000+0000
- start: 2019-07-02 16:33:29.005395122000+0000
end: 2019-07-02 17:52:06.375957744000+0000
- start: 2019-07-02 11:09:00.728128801000+0000
end: 2019-07-02 12:40:24.872332712000+0000
- start: 2019-07-02 10:53:09.112838235000+0000
end: 2019-07-02 10:53:23.469784638000+0000
- header: Modify my timestamp with ss
timestamps:
SCHEDULED: 2019-07-06
- header: xxx xx xxxx xxxxxx xxxxxxx
state-history:
- new-state: TODO
timestamp: 2019-07-03 06:44:03.329347470000+0000
- header: xxxx xxxxx xxxxx xxxxxxx xxxxxx xxx xxxxxx
timestamps:
SCHEDULED: 2019-07-03
- header: xxxxxx xxx xxxxxx
state-history:
- new-state: TODO
timestamp: 2019-07-03 06:43:56.923525622000+0000
- header: xxx xx xxxx xxx xxxxx
state-history:
- new-state: TODO
timestamp: 2019-07-03 06:43:57.982459378000+0000
When I try to change the SCHEDULED timestamp for the 2nd item, the cursor gets placed before the colon:
SCHEDULED:
^-- cursor between D and :
It would be nice to have a convenience function like convDoneAndWaitForResponse for when you get a response from someone and you're still waiting for another one.
There is already an interactive next action report, but advanced users will use the work command instead, so it would be nice to have an interactive report for it too. @aniketd
This depends on lazy un-collapsing because otherwise it would take ages in the home directory
This would essentially only be some adding to and removing from the base path of the file browser cursor.
Between 800 and 1000 files, a problem starts to occur:
uncaught exception: SqliteException
SQLite3 returned ErrorError while attempting to perform prepare "DELETE FROM \"server_file\" WHERE (\"user\"=?) AND ((\"uuid\" IS NULL OR \"uuid\" NOT IN (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)))": too many SQL variables
I have started by making a failing test at sync-bug.
Currently every file is checked upon every sync, but really only the files that got any modification should be changed.
This depends on: NorfairKing/mergeful#1
(well not really but there's no need to implement this twice so we might as well start there.)
From comments on #39:
How do you deal with recurring tasks(is that what the scheduler is for?)? Ideally, there'd be 2 types of recurring tasks. Those that repeat on fixed periods or those that repeat a fixed time after marking the previous occurrence as done. E.g., I have an "Enter Bank Statements" task in Finances that is scheduled for the 1st of the month. When I mark it as done, I create a duplicate task and schedule it for the first of the next month. For the second type, say I want to clean or organize weekly. After marking a "sweep!" task as done, I'd like to auto-add another "sweep!" task that is auto-scheduled on today + 7 days. But again, I feel like there'd be a clutter of DONE tasks after months of usage - maybe I should split it into projects by year, e.g. finances-2020.smos?
Yes that's what the scheduler is for. It doesn't work yet, but feel free to write up an issue.
I agree with your multiple types of recurring tasks. I call them hairdresser-recurrent and rent-recurrent.
I'd like to get some more time to work on the scheduler but life gets in the way :)
Currently I have put a task in my weekly review template (that I copy around during the previous weekly review) to create a project to pay my bills (from another template).
So I'd have bills-17.smos for the bills project of the 17th week of the year.
Essentially, I'd like to automatically add new tasks on specific periods(e.g., start of next month, start of next quarter, start of next year) when a task is marked as done and after fixed durations(7 days after marking as done, 1 month after marking as done).
This would make finding the right file easier.
It will need some work on filtering in cursor-dirforest.
We want to be able to fuzzy-search on the filename but possibly also on some of the contents?
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Google
Google ❤️ Open Source for everyone.
Alibaba
Alibaba Open Source for everyone
D3
Data-Driven Documents codes.
Tencent
China tencent open source team.