bud/i3term
1
0
Fork 0
Code Issues Pull requests 1 Releases 2 Wiki Activity

Add kitty terminal support #3

Open
gmardom wants to merge 1 commit from gmardom/next into next
pull from: gmardom/next
merge into: bud:next
Conversation 2 Commits 1 Files changed 16 +63 -62
gmardom commented 2024-04-01 17:45:11 +00:00 (Migrated from github.com)
Copy link
No description provided.
👍 1
budRich commented 2024-04-01 19:09:29 +00:00 (Migrated from github.com)
Copy link

cool, i will try this out before merching, but it looks good. There is one thing though, and this is on me, i have never mentioned this, but the documentation (includes man page and readme.md) is generated from the stuff in docs/ . i just include the """"compiled""" manpage/readme for convenience and also remove make dependencie go-md2man , but if you have that command, i think you can generate new Readme and manpage with , make readme , make manpage

cool, i will try this out before merching, but it looks good. There is one thing though, and this is on me, i have never mentioned this, but the documentation (includes man page and readme.md) is generated from the stuff in docs/ . i just include the """"compiled""" manpage/readme for convenience and also remove make dependencie `go-md2man` , but if you have that command, i think you can generate new Readme and manpage with , make readme , make manpage
gmardom commented 2024-04-01 20:10:27 +00:00 (Migrated from github.com)
Copy link

i just include the """"compiled""" manpage/readme for convenience and also remove make dependencie go-md2man, but if you have that command, i think you can generate new Readme and manpage with , make readme , make manpage

At first I started changing all the files by hand, then I dug into the Makefile a bit and made new readme and man page that way. If you look on my fork's readme, it should reflect the changes I made. This one is on me, but I should've split the commits into feature and documentation. I got kind of rusty with my git-fu and out of frustration I commited this as just one thing.

> i just include the """"compiled""" manpage/readme for convenience and also remove make dependencie `go-md2man`, but if you have that command, i think you can generate new Readme and manpage with , make readme , make manpage At first I started changing all the files by hand, then I dug into the Makefile a bit and made new readme and man page that way. If you look on my [fork's](https://github.com/gmardom/i3term) readme, it should reflect the changes I made. This one is on me, but I should've split the commits into feature and documentation. I got kind of rusty with my git-fu and out of frustration I commited this as just one thing.
👍 1
This pull request can be merged automatically.
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin gmardom/next:gmardom/next
git switch gmardom/next

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch next
git merge --no-ff gmardom/next
git switch gmardom/next
git rebase next
git switch next
git merge --ff-only gmardom/next
git switch gmardom/next
git rebase next
git switch next
git merge --no-ff gmardom/next
git switch next
git merge --squash gmardom/next
git switch next
git merge --ff-only gmardom/next
git switch next
git merge gmardom/next
git push origin next
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
bud/i3term!3
No description provided.