aashcan
Re:Uses for an old Android device
on Tuesday August 09, 2022 @08:56AM (#32397151)
Thanks for your work! Is one of the first apps I purchased :)
Re:My Mathematics PhD research workflow: LaTeX notes and instant pdf r...
on Monday April 11, 2022 @07:15AM (#30987131)
What no TiKz? :o
Re:Incident with GitHub Actions, API Requests, Git Operations, Issues ...
on Tuesday August 10, 2021 @11:50AM (#28130319)
meh, here I thought my git-foo was wrong.
Ran garbage clearance for nothing also. :-(
Re:Ask HN: How do you switch off from work, particularly when working ...
on Wednesday August 19, 2020 @07:21AM (#24209227)
Head out for a five/ten min walk before you begin working to mimic a commute to work..
Re:Disable new Slack WYSIWYG editor with this bookmarklet
on Friday November 29, 2019 @06:59AM (#21663820)
Just got another note from them:
We really appreciate your feedback, and we hear your frustration.
We're sorry for the impact this is having on your ability to communicate with your team and on your overall productivity.
We made a mistake by forcing everyone into this feature without providing an opt-out for customers like you: people for whom the existing behavior was working just fine.
We've started working on a preference that will let you return to the previous message composer.
We don't have a specific release date to share right now — it's this team's top and only priority, however, and we expect to have it available on the desktop within a couple of weeks, with Android following shortly thereafter.
We will follow up with another note when this option is available to you, and we'll include instructions on how to enable it.
Again, we're sorry for the disruption and we're grateful for the feedback.
We missed the mark on this feature! We will do our best to learn from this and avoid similar mistakes in the future.
Re:Slack’s new WYSIWYG input box is terrible
on Thursday November 21, 2019 @05:53AM (#21592973)
Just wrote in,
Thanks for sharing your experience with our new formatting UI. I'm sorry to hear it's been a little disruptive so far.
There isn't a way to revert to the old formatting method, I'm afraid.
We don't currently have plans to make the new formatting configurable
though we are carefully considering all our customers' feedback.
Re:Async-await on stable Rust
on Thursday November 07, 2019 @11:44AM (#21474772)
Could you share some resources? I'm trying to move a Hyper + Tokio-core + Futures project to the newer versions and am struggling..
Re:Async-await on stable Rust
on Thursday November 07, 2019 @10:55AM (#21474258)
All we need are a few migration guides for Tokio, Hyper, Futures...
Re:Firefox 70
on Tuesday October 22, 2019 @10:36AM (#21324061)
There used to be the Dictionary Switcher addon, but doesn't work >v57.
An alternative I found was https://addons.mozilla.org/en-GB/firefox/addon/automatic-spe...
Re:PuTTY 0.73
on Tuesday October 01, 2019 @01:07PM (#21127809)
Took them only about 30 odd years..
[0] https://devblogs.microsoft.com/commandline/extended-eol-in-n...
Re:Train speed record set between London and Bristol
on Monday September 30, 2019 @11:11AM (#21116172)
Not speedy even if you go back ~ 90 years ;-)
https://en.wikipedia.org/wiki/Schienenzeppelin
Re:Universal Resume Template
on Tuesday September 10, 2019 @06:30PM (#20934548)
And then you start playing around with TikZ...
Re:Ripgrep 11 Released
on Tuesday April 16, 2019 @06:00AM (#19672348)
Atom's fuzzy finder also uses ripgrep as of 1.37.0
Still stick with Atom as my main text/code editor here. I started out with it mainly to write LaTeX, but since do most of my code editing also in Atom. I looked at VSCode back in '17 but found it quite clunky and not as intuitive as Atom. Things like changing key-binding based on a profile for example needs a quick Google - or maybe I am just slow!
I keep going back now and then to VS Code especially when I need to use the debugger to step through some code. But otherwise, my workflow since has evolved around the little niggles of Atom(like having to open separate terminal windows) so I don't feel the need to switch.
>The fuzzy finder’s project crawling performance has been improved dramatically by switching to a ripgrep-powered backend. This is most noticeable in projects with large numbers of files - for example, we measured a 14x speed boost in a project with 270K files.
Another leaf out of VS Code's book?
Re:Show HN: Open-sourcing my wedding website on my first anniversary
on Thursday November 29, 2018 @08:00AM (#18559842)
Nice site, you might want to quickly fix some typos and spaces b/w punctuations (periods and commas) in your text!