mirror of
https://github.com/soywod/himalaya.git
synced 2025-04-21 16:53:39 +00:00
Compare commits
No commits in common. "master" and "v1.1.0" have entirely different histories.
6 changed files with 372 additions and 270 deletions
3
.github/workflows/release-on-demand.yml
vendored
3
.github/workflows/release-on-demand.yml
vendored
|
@ -9,9 +9,10 @@ on:
|
|||
required: true
|
||||
default: ubuntu-latest
|
||||
options:
|
||||
- ubuntu-24.04
|
||||
- ubuntu-latest
|
||||
- macos-13
|
||||
- macos-14
|
||||
- windows-latest
|
||||
target:
|
||||
description: Architecture
|
||||
type: choice
|
||||
|
|
|
@ -66,4 +66,4 @@ secret-lib.path = "/path/to/core/secret"
|
|||
|
||||
## Commit style
|
||||
|
||||
Starting from the `v1.0.0`, Himalaya CLI tries to adopt the [conventional commits specification](https://www.conventionalcommits.org/en/v1.0.0/#summary).
|
||||
Starting from the `v1.0.0`, Himalaya CLI tries to adopt the [conventional commits specification](https://github.com/conventional-commits/conventionalcommits.org).
|
||||
|
|
600
Cargo.lock
generated
600
Cargo.lock
generated
File diff suppressed because it is too large
Load diff
13
Cargo.toml
13
Cargo.toml
|
@ -55,16 +55,3 @@ toml = "0.8"
|
|||
tracing = "0.1"
|
||||
url = "2.2"
|
||||
uuid = { version = "0.8", features = ["v4"] }
|
||||
|
||||
[patch.crates-io]
|
||||
imap-codec.git = "https://github.com/duesee/imap-codec"
|
||||
|
||||
email-lib.git = "https://github.com/pimalaya/core"
|
||||
imap-client.git = "https://github.com/pimalaya/imap-client"
|
||||
keyring-lib.git = "https://github.com/pimalaya/core"
|
||||
mml-lib.git = "https://github.com/pimalaya/core"
|
||||
oauth-lib.git = "https://github.com/pimalaya/core"
|
||||
pgp-lib.git = "https://github.com/pimalaya/core"
|
||||
pimalaya-tui.git = "https://github.com/pimalaya/tui"
|
||||
process-lib.git = "https://github.com/pimalaya/core"
|
||||
secret-lib.git = "https://github.com/pimalaya/core"
|
||||
|
|
18
README.md
18
README.md
|
@ -295,11 +295,11 @@ You can also manually edit your own configuration, from scratch:
|
|||
folder.aliases.trash = "[Gmail]/Trash"
|
||||
|
||||
backend.type = "imap"
|
||||
backend.host = "imap.gmail.com"
|
||||
backend.port = 993
|
||||
backend.login = "example@gmail.com"
|
||||
backend.auth.type = "password"
|
||||
backend.auth.raw = "*****"
|
||||
backend.type.host = "imap.gmail.com"
|
||||
backend.type.port = 993
|
||||
backend.type.login = "example@gmail.com"
|
||||
backend.type.auth.type = "password"
|
||||
backend.type.auth.raw = "*****"
|
||||
|
||||
message.send.backend.type = "smtp"
|
||||
message.send.backend.host = "smtp.gmail.com"
|
||||
|
@ -546,7 +546,7 @@ You can also manually edit your own configuration, from scratch:
|
|||
- `Reply-To`: represents the address the receiver should reply to instead of the `From` header
|
||||
- `Cc`: represents the addresses of the other receivers (carbon copy)
|
||||
- `Bcc`: represents the addresses of the other hidden receivers (blind carbon copy)
|
||||
|
||||
|
||||
An address can be:
|
||||
|
||||
- a single email address `user@domain`
|
||||
|
@ -668,12 +668,6 @@ You can also manually edit your own configuration, from scratch:
|
|||
5. try to guess (`imap.example.com`, `smtp.example.com`…)
|
||||
</details>
|
||||
|
||||
<details>
|
||||
<summary>How to disable color output?</summary>
|
||||
|
||||
Simply set the environment variable NO_COLOR=1
|
||||
</details>
|
||||
|
||||
## Sponsoring
|
||||
|
||||
[](https://nlnet.nl/)
|
||||
|
|
6
flake.lock
generated
6
flake.lock
generated
|
@ -40,11 +40,11 @@
|
|||
"pimalaya": {
|
||||
"flake": false,
|
||||
"locked": {
|
||||
"lastModified": 1737984647,
|
||||
"narHash": "sha256-qcxytsdCS4HfyXGpqIIudvLKPCTZBBAPEAPxY1dinbU=",
|
||||
"lastModified": 1736516871,
|
||||
"narHash": "sha256-ZQ85Xx+HKVq76jROEMNnCh+6jmlznG4gK1wEjnCm6/A=",
|
||||
"owner": "pimalaya",
|
||||
"repo": "nix",
|
||||
"rev": "712a481632f4929d24a34cb5762e0ffdc901bd99",
|
||||
"rev": "e26314178f3232d83f463102c2b7774c6a702a94",
|
||||
"type": "github"
|
||||
},
|
||||
"original": {
|
||||
|
|
Loading…
Add table
Reference in a new issue