~gildarts

Indianapolis, IN

https://orbital.rocks

~gildarts/inspector

Last active 5 months ago
View more

Recent activity

Re: API to set license for repo 7 days ago

From gildarts to ~sircmpwn/sr.ht-discuss

On 1/20/2021 10:17 PM, Eli Schwartz wrote:
> I solved this problem by writing a simple wrapper around git which 
> prevents a lot of things from being checked out into ~/, including the 
> .git/ directory as I don't believe it's wise to make git commands fail 
> outside of a git repo by... acting on your dotfiles repo.

I've always just checked out my dotfiles repo to `~/.dotfiles` and 
symlinked the files into `~`. Is there a compelling reason to not go 
that route? I just seemed cleaner to me. Only difficulty is creating the 
symlinks, but you can script that or use other methods.

-gildarts

Re: "Elasticsearch does not belong to Elastic" 7 days ago

From gildarts to ~sircmpwn/public-inbox

On 1/20/2021 3:39 PM, Adrien Glauser wrote:
> Now intuitively there is a gap between:
> a) you as a company want to offer your code to a community of volunteers 
> and consumers, FOSS-style; and
> b) you as a company don't have the market power yet — too few employees, 
> too little capital — to compete with bigger companies that might use 
> your code in their services without contributing or giving back in any 
> way, where the competition would be in terms of services, uptime, 
> support, availability, etc.

I haven't contributed to Elastic at all and don't use it, so take this 
however you like.

 From my perspective, it seems like a bait and switch to use community

Re: [PATCH git-send-email.io] Fix mailing list names in stage-2-success 12 days ago

From gildarts to ~sircmpwn/sr.ht-dev

On 1/15/2021 10:20 AM, Drew DeVault wrote:
> Sorry, I would prefer to have these sent to my public inbox for the time
> being.

Should probably change the preceding line to reflect that then.

 > If [...], please write to sr.ht-discuss:

Just for consistency.

-gildarts

Re: Dark mode feedback a month ago

From gildarts to ~sircmpwn/sr.ht-discuss

On 12/16/2020 6:55 PM, Cadence Ember wrote:
> Patch feedback has a bright edge.
> https://lists.sr.ht/~sircmpwn/sr.ht-discuss/patches/3677#%3C87h8ediyj1.fsf@jb55.com%3E
> 

Looks like the the feedback class border needs to be set to the same as 
pre element background color.

Something like the below when in dark mode. Unsure where that needs to 
be changed though. Will be looking later if Drew or someone else doesn't 
beat me to it.

```css
.feedback {

Re: Night mode for sr.ht? a month ago

From gildarts to ~sircmpwn/sr.ht-discuss

On 12/4/2020 7:31 AM, Journeyman wrote:
> 
> I believe previous discussion here:
> https://lists.sr.ht/~sircmpwn/sr.ht-discuss/%3C20190208130523.tb5gtfp2j2p75wh2%40gabriel%3E
> 

Per the previous discussion, at least some of the argument against a 
dark mode was browser support. It appears that `prefers-color-scheme` is 
pretty well supported at this point [1].

As for testing it as a user style first, I don't know where that is at 
right now.

-gildarts

[RFC PATCH core.sr.ht] Fix alignment and sizing of header anchor tags 3 months ago

From gildarts to ~sircmpwn/sr.ht-dev

- Switch to `inherit` for font-size to allow the achor to change as the
  font-size of the anchor changes
- Switch to relative spacing so that the position change also adjusts
  with header text size.
- Remove margin rule that appeared to be causing issues aligning the
  header properly.
---
 srht/scss/base.scss | 8 ++------
 1 file changed, 2 insertions(+), 6 deletions(-)

diff --git a/srht/scss/base.scss b/srht/scss/base.scss
index 3235e63..dd35633 100644
--- a/srht/scss/base.scss
+++ b/srht/scss/base.scss
[message trimmed]

Re: Missing spacing on top-level Markdown headings 3 months ago

From gildarts to ~sircmpwn/sr.ht-discuss

On 9/28/2020 4:12 PM, наб wrote:
> I've ported it to the SCSS and posted to sr.ht-dev@ as
>    <20200928200807.in3j63qkdcwhd4tx@tarta.nabijaczleweli.xyz>
> 

Saw the patch, looks good!

-gildarts

Re: Missing spacing on top-level Markdown headings 4 months ago

From gildarts to ~sircmpwn/sr.ht-discuss

On 9/25/2020 7:32 AM, Ivar Løvlie wrote:
> Would this work:
> -- >8 --
> .markdown h1 *:not(:first-child),
> -- >8 --
> 

Thinking this might be better. Should avoid matching cases where there 
is an anchor in a header other than the one wrapping the badge.

.markdown h1 img,
.markdown h2 img,
.markdown h3 img,
.markdown h4 img,

Re: [PATCH core.sr.ht] Remove extra # from toc generation 4 months ago

From gildarts to ~sircmpwn/sr.ht-dev

On 9/15/2020 12:09 PM, Drew DeVault wrote:
> Does this extract all of the links or just the first one?
> 

Just the first one from my testing.

```
 >>> soup = BeautifulSoup("<h1><a>#</a><a>test</a></h1>", "html5lib")
 >>> h_tag = soup.h1.extract()
 >>> print(h_tag)
<h1><a>#</a><a>test</a></h1>
 >>> h_tag.a.extract()
<a>#</a>
 >>> print(h_tag)

[PATCH core.sr.ht] Remove extra # from toc generation 4 months ago

From gildarts to ~sircmpwn/sr.ht-dev

Sorry for the confusion on my end with the previous patches.

---
 srht/markdown.py | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/srht/markdown.py b/srht/markdown.py
index 55c0755..ba0ff28 100644
--- a/srht/markdown.py
+++ b/srht/markdown.py
@@ -12,7 +12,7 @@ import mistletoe as m
from mistletoe.span_token import SpanToken, RawText
import re

[message trimmed]