list

var ListCmd = &cobra.Command{
	Use:   "list [# runid] [runner]",
	Short: "List notes in particular order",
	Long: `List notes in particular order

  === Listing ===

  By default, the list is ordered by note's modify time.
  If given the "-t" option, it will using the relevant order.

  Listing Example:
    $ loli list
    $ loli list -t <term>

  === Run Command ===

  After some listing, user can also choice the "runid" and "runner" to
  open (or processing) a particular note.

  Running Example:
    $ loli list 3 ls        # run "ls <note-3>"
    $ loli list 1 vim       # run "vim <note-1>"
    $ loli list -p 2 1 cat  # run cat with <the first note in page 2>

  User can omit the "runner" if already assigned in configuration file.

  By default, the *Run-Path* will be appended to the tail of runner. But
  it can also be assigned to particular location by using the placeholder
  "{}".

  === The Run-Path ===

  List command also offer multiple type of run-path.

  The run-path Type:
    1. Content Path: the filepath contain the note's content. Good for
       editing or viewing.
    2. Parent Directory: the dir path contain the note's entry. Good for
       files browsing.
    3. Attachment Directory: the dir path contain the complex-note's
       attachments. Good for tweak the attachments.
    4. Entry Path: the entry path of the notes. Good for deleting or
       moving.

  By default, list command using Content Path as run-path.
`,
	PreRun: func(cmd *cobra.Command, args []string) {
		inAttMode, _ := cmd.Flags().GetBool("attachment-dir")
		inDirMode, _ := cmd.Flags().GetBool("parent-dir")
		inEntryMode, _ := cmd.Flags().GetBool("entry")

		assertGoodInput(inAttMode, inDirMode, inEntryMode)

		if isPrintMode(args) {
			assertGoodPrintModeInput(
				inAttMode, inDirMode, inEntryMode,
			)
		}
	},
	Run: run,
}