I am Enan, a CSE graduate and an OSS enthusiast. I use vim and live in the terminal.
You can reach me at 3nan.ajmain@gmail.com.
Or you can initiate a public discussion at ~enan/public-inbox@lists.sr.ht.
From Enan Ajmain to ~sircmpwn/sr.ht-discuss
As others have already pointed out, the problem is not with your git command but with your zsh command. Others have suggested ways to bend zsh to your will, but I suggest you simply don't use zsh. If you weren't able to realize the problem was with zsh globbing, you aren't a zsh power-user. You should stick with a more de-facto solution, ala bash. If you _are_ a zsh power-user, then learn more about zsh. -- Enan 3nan.ajmain@gmail.com https://www.github.com/3N4N
From Enan Ajmain to ~sircmpwn/sr.ht-discuss
On Sat, 28 Jan 2023 18:40:40 -0500 Antoine Fauchié <antoine@quaternum.net> wrote: > If you want do discover what is Soft Serve, just type `ssh git.charm.sh` > on your favorite terminal. Interesting. Thanks for the info; didn't know about this. It runs quite slow. I was wondering if it's a limitation of ssh speed or a limitation of the TUI app itself. -- Enan 3nan.ajmain@gmail.com https://git.sr.ht/~enan/
From Enan Ajmain to ~sircmpwn/sr.ht-discuss
On Wed, 11 Jan 2023 00:40:26 -0800 y8 <fee9ru@gmail.com> wrote: > For GitHub, I have foo@users.noreply.github.com setup in my git > config. I also have "Keep my email addresses private " and "Block > command line pushes that expose my email " set. When I have a question about a codebase or a specific commit, I look for the email of the maintainer or the committer to contact them. I have sometime seen some people using noreply address in GitHub and was annoyed to no end. This is not to devalue/deprioritize your situation; this is to share scenarios where the very system you say is problematic is for others indispensable. I hope you find other ways to circumvent your problem (using untraceable info for public use, as Devault suggested, seems to be a good solution).
From Enan Ajmain to ~sircmpwn/sr.ht-discuss
On Mon, 12 Dec 2022 10:47:57 +0100 "Moritz Poldrack" <moritz@poldrack.dev> wrote: > On Mon Dec 12, 2022 at 10:46 AM CET, Enan Ajmain wrote: > > Did you mean something else? Some other argument perhaps? > No I thought basically about that. Are you sure there are no more > references to this commit? You're right. There were other refs to this commit. I had to clean the reflog entries: git reflog expire --expire=90.days.ago --expire-unreachable=now --all --
From Enan Ajmain to ~sircmpwn/sr.ht-discuss
On Mon, 12 Dec 2022 15:55:15 +0600 Enan Ajmain <3nan.ajmain@gmail.com> wrote: > My knowledge says it should be C1 and C2, but the word you chose, > "past", makes it seem like C4 and C5. I mixed up the commit numbers. It should be: My knowledge says it should be C4 and C5, but the word you chose, ^^^^^^^^^ "past", makes it seem like C1 and C2. ^^^^^^^^^ Also, I forgot to CC the list. Below is my original message.
From Enan Ajmain to ~sircmpwn/sr.ht-discuss
On Mon, 12 Dec 2022 09:54:07 +0100 "Moritz Poldrack" <moritz@poldrack.dev> wrote: > I think the usual thing to do is to wait for git gc to run or running > it manually. I did each of these: git gc git gc --prune=now git gc --prune=now --aggressive But I can still reach the comprosing commit through git show <commit-hash>:path/to/file.ext Did you mean something else? Some other argument perhaps?
From Enan Ajmain to ~sircmpwn/sr.ht-discuss
Sometimes I need to delete a commit from a git repo. Mistakenly adding private info to the commit is the major reason for such a necessity. I can rebase and edit the commit, but the original commit, let's call it the compromising commit, is still accessible, in both the local git repo and the upstream, via the commit hash. What's the procedure in such cases? -- Enan 3nan.ajmain@gmail.com https://git.sr.ht/~enan/ https://www.github.com/3N4N
From Enan Ajmain to ~sircmpwn/public-inbox
On Fri, 9 Dec 2022 18:17:32 +0100 Arnaud Vallette d'Osia <arnaudv6@gmail.com> wrote: > Hi > have you ruled-out WSL? > I do most of the stuff from a WSL terminal I'm doomed to using windows. I do use aerc in WSL. But the main attaction of it, for me, was the ability to easily change current working directory and apply a patch. And although WSL is a better development environment, I still use native Windows environment for at least half of my dev work. So I'd prefer to have an email client that works on both platforms. To bring this email thread to an end, I wanna conclude by saying that I've currently chosen Claws as my preferred email client. It's cross
From Enan Ajmain to ~sircmpwn/sr.ht-discuss
On Wed, 07 Dec 2022 13:01:18 +0900 Nguyễn Gia Phong <mcsinyx@disroot.org> wrote: > Just checking: since it asks for AUTH and STARTTLS, I suppose you have > > [sendemail] > smtpencryption = tls > smtpserverport = 587 I don't know what's causing Ryan's problem, but since I didn't have any issue yet, maybe my config can help: [sendemail] smtpServer = smtp.gmail.com ; or whatever is your email server smtpServerPort = 587
From Enan Ajmain to ~sircmpwn/public-inbox
On Fri, 25 Nov 2022 19:18:45 +0100 Adolfo Santiago <epoch@nixnetmail.com> wrote: > Did you check if aerc is good enough for this? I don't know how good the > support would be for Windows, but you can always send patches, just in > case they get accepted. Or just keep your own copy and get changes for > upstream. I really like aerc. Unfortunately it's not supported on Windows. I tried building it with Msys, even succeeded by changing some stuff in one of its dependencies and some sanity checks in aerc source. I managed to get the main UI open, but it didn't connect to my email account. The author, rjarry, conjectured it may be because one of the dependencies doesn't have Windows support.