summaryrefslogtreecommitdiff
path: root/README.md
diff options
context:
space:
mode:
authorPaul Buetow <paul@buetow.org>2025-02-11 05:32:40 +0200
committerPaul Buetow <paul@buetow.org>2025-02-11 05:32:40 +0200
commitfe4b9adab9f792ced2842decde7a4af9f762dd9f (patch)
tree4f27e6c4d276716b3cf047f8ec458fdc7c74a44a /README.md
parent07e87a4a1f6a5345a14caa4b21ace95f72c068ac (diff)
add comment
Diffstat (limited to 'README.md')
-rw-r--r--README.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/README.md b/README.md
index be05340..8136987 100644
--- a/README.md
+++ b/README.md
@@ -218,7 +218,7 @@ Hello World :-)
### The `gosc` binary
-`gosc` stands for Gos Composer and will simply launch your `$EDITOR` on a new text file in the gosDir. It is a quick way of composing new posts. Once composed, it will ask for your confirmation on whether the message should be queued or not, and from there it will continue normally like the regular `gos` command.
+`gosc` stands for Gos Composer and will simply launch your `$EDITOR` on a new text file in the gosDir. It's the same as running `gos --compose` realy. It is a quick way of composing new posts. Once composed, it will ask for your confirmation on whether the message should be queued or not, and from there it will continue normally like the regular `gos` command.
## How Queueing Works in Gos