For completeness, I'll mention that there was a short-lived effort 13 years
ago to make a catalog of keywords to use; see
https://wiki.sagemath.org/TracKeywords?action=info
On Thursday, September 28, 2023 at 12:46:57 PM UTC-7 Matthias Koeppe wrote:
> On Trac, keywords were completely
it should be possible to search for patterns in commit messages across PRs
- this info is in the git tree.
GitHub metadata is harder to search, and I am quite surprised how limited
their search options are.
On Thu, 28 Sept 2023, 20:46 Matthias Koeppe,
wrote:
> On Trac, keywords were completely
On Trac, keywords were completely free-form; there was nothing to click,
and there wasn't an agreement whether multiple keywords are separated by
whitespaces or commas or semicolons.
In the migration, we did a frequency count of words and phrases used there
and transformed some of the most
I would like to have trac keywords back. Searching issues in github seems
quite difficult, for example, it seems that wildcards are not supported:
"is:pr is:open lazypower" finds nothing wereas "is:pr is:open
lazypowerseries" does.
On trac, I used keywords to collect the issues that
+ 1 for getting rid of the preparsing of \
It is particularly annoying when typing (usually long) expressions like
f(x) = x + \
1
in an input cell of a Jupyter notebook. If the \ is followed by a blank
space, one gets
Cell In [22], line 1
__tmp__=var("x"); f =
I have created a PR: https://github.com/sagemath/sage/pull/36354
On Monday, September 25, 2023 at 11:36:46 AM UTC+5:30 Dima Pasechnik wrote:
>
>
> On Mon, 25 Sept 2023, 06:59 Saatvik Rao, wrote:
>
>> Hello developers,
>>
>> I am currently doing a project course that involves making active
>>
On Wednesday, September 27, 2023 at 6:19:16 PM UTC-4 William Stein wrote:
Hi,
I'm the guilty party who added \ to Sage notation in the first place,
and I would definitely vote to *remove* it. I wish I had
never added it in the first place. Nils has some very good points!
I do think it's
