From Evan Gates to ~martanne/devel
Add filenames .bashrc and .bash_profile to the filetype plugin section for bash so they use bash syntax highlighting automagically. --- lua/plugins/filetype.lua | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lua/plugins/filetype.lua b/lua/plugins/filetype.lua index 18767ec..a459601 100644 --- a/lua/plugins/filetype.lua +++ b/lua/plugins/filetype.lua @@ -40,7 +40,7 @@ vis.ftdetect.filetypes = { ext = { "%.awk$" }, }, bash = { [message trimmed]
From Evan Gates to ~martanne/devel
On Thu May 5, 2022 at 9:16 AM MDT, Matěj Cepl wrote: > This probably could be closed, couldn't it? It seems like it has been > done in 0eb069f51fff4dc934d4043b2540fa20147307b6. Well, I replied with the custom header to mark the patch applied, but it didn't work. I'll see if I can get a better understanding of what permissions I'd need then ask martanne if he could grant them.
From Evan Gates to ~martanne/devel
On Thu May 5, 2022 at 9:16 AM MDT, Matěj Cepl wrote: > This probably could be closed, couldn't it? It seems like it has been > done in 0eb069f51fff4dc934d4043b2540fa20147307b6. I've added the X-Sourcehut-Patchset-Update:APPLIED header to see if that will mark this as applied correctly.
From Evan Gates to ~sircmpwn/sr.ht-discuss
I have just been given access to maintain a piece of software. The original owner is too busy and has handed over permissions to the repos so I can apply patches etc. We want to keep using the original repo instead of forking it to avoid confusion for the users. The repo does have the right files to kick off builds, but the original owner does not have a paid account, so the builds don't run. I do have a paid account, so I'd like to be able to run builds. Since I'm now maintaining this piece of software, is there any way for me to take over ownership in a way that will allow builds to run, but without moving the project/repos?
From Evan Gates to ~sircmpwn/sr.ht-discuss
I was experimenting with the email integration with the ticket system. I was able to send an email and have it show up as a comment on a ticket. I received that comment as an email. I replied to the email, assuming my reply would show up as a comment on the ticket. After it didn't show up I went back and realized that the Reply-To address was Drew: Reply-To: Drew DeVault <sir@cmpwn.com> From: "~martanne" <outgoing@sr.ht>, <outgoing@sr.ht> Date: Tue, 03 May 2022 17:20:50 +0000 Message-Id: <CJQASDVH3MHN.LB81SMIAEJKI@todo> Subject: Re: ~martanne/vis#4: Dummy ticket To: "~emg" <evan.gates@gmail.com>
From Evan Gates to ~rjarry/aerc-devel
By using :compose -H <header> a user should be able to add arbitrary headers to an email. The existing implementation from 5b523880b4b4cd2abd9457b4b09c384af33be14b added the headers as lines to the beginning of the body. These lines were not interpreted as headers anywhere and ended up as plain text in the body of the email. Fix the code to parse and add the headers correctly. --- Changes in v2: - Handle EOF from ReadMessage when body is empty commands/account/compose.go | 17 +++++++++++++++-- 1 file changed, 15 insertions(+), 2 deletions(-) [message trimmed]
From Evan Gates to ~rjarry/aerc-devel
On Fri Apr 1, 2022 at 2:43 PM MDT, Evan Gates wrote: > By using :compose -H <header> a user should be able to add > arbitrary headers to an email. The existing implementation from > 5b523880b4b4cd2abd9457b4b09c384af33be14b added the headers as lines > to the beginning of the body. These lines were not interpreted as > headers anywhere and ended up as plain text in the body of the email. > Fix the code to parse and add the headers correctly. > --- > > NOTE: I do not know if this worked at one point in the past and broke. > I tried to build and run the commit that introduced the feature > but aerc hung. I can spend more time doing a git bisect if that > is helpful.
From Evan Gates to ~rjarry/aerc-devel
By using :compose -H <header> a user should be able to add arbitrary headers to an email. The existing implementation from 5b523880b4b4cd2abd9457b4b09c384af33be14b added the headers as lines to the beginning of the body. These lines were not interpreted as headers anywhere and ended up as plain text in the body of the email. Fix the code to parse and add the headers correctly. --- NOTE: I do not know if this worked at one point in the past and broke. I tried to build and run the commit that introduced the feature but aerc hung. I can spend more time doing a git bisect if that is helpful. commands/account/compose.go | 13 +++++++++++-- [message trimmed]
From Evan Gates to ~rjarry/aerc-devel
I went into gmail and moved the entire thread to the inbox. After that the thread appears as it should. Monday 06:45 AM Andreas Luik parameter expansion null check fails for arrays when [*] or [@] is used 08:42 AM Chet Ramey ├─> Tuesday 03:51 PM L A Walsh └─> 01:25 AM Ilkka Virta └─> 05:56 AM Robert Elz ├─> 02:48 AM L A Walsh └─> 06:26 AM Robert Elz ├─> 05:38 AM Greg Wooledge └─> 06:13 AM Alex fxmbsw7 Ratc └─> If I delete that first message, then the thread disappears.
From Evan Gates to ~rjarry/aerc-devel
$ aerc -v aerc 0.9.0-2-ge566480 I opened aerc and saw the following list of emails: 07:42 AM Ondřej Synáček O Re: download all attachments 07:37 AM Tim Culverhouse O Re: download all attachments 07:31 AM Nguyễn Gia Phong O Re: ~rjarry/aerc-discuss? 06:13 AM Alex fxmbsw7 Ratc O Re: parameter expansion null check fails for arrays when [*] or [@] is used 05:56 AM Robert Elz O Re: parameter expansion null check fails for arrays when [*] or [@] is used 06:26 AM Robert Elz O Re: parameter expansion null check fails for arrays when [*] or [@] is used 05:38 AM Greg Wooledge O Re: parameter expansion null check fails for arrays when [*] or [@] is used 02:48 AM L A Walsh O Re: parameter expansion null check fails for arrays when [*] or [@] is used