# Start a new discussion

## Not signed in

Want to take part in these discussions? Sign in if you have an account, or apply for one below

## Site Tag Cloud

Vanilla 1.1.10 is a product of Lussumo. More Information: Documentation, Community Support.

• CommentRowNumber101.
• CommentAuthorUrs
• CommentTimeJan 16th 2021

A bibtex-like functionality might be good, but seems like a tall order, as this will not be dealt with by a handful lines of code. This might instead be something to outsource to a hired programmer once we have the donation mechanism in place, from March on?

Meanwhile, since bibtex is mostly a glorified include-mechanism, we can easily emulate something close right now:

Just write bibitems one by one into nLab pages, using some standardized naming convention, and then !include these where desired.

As an example for what I mean, I just created an item Quillen1967AHT-ref and included it into the list of references at model category (first item there).

• CommentRowNumber102.
• CommentAuthorUrs
• CommentTimeJan 17th 2021

On a more elementary note:

The vertical spacing above the first bullet list items on second nesting level is too small.

An example now in the Sandbox.

This might seem petty, but with hyperlinks and/or formulas in there it shows up a lot in our entries and looks bad, I think.

1. Thanks for raising! Just to let you know that I have seen these things and will respond/address them as soon a I get a chance.

• CommentRowNumber104.
• CommentAuthorUrs
• CommentTimeJan 26th 2021

Thanks, Richard.

I feel bad for raising yet one more issue. So not to rush, but just to record it:

I managed to make an entry – with the (beautiful, you must admit) title MΩΩSU(n) – which can’t be edited: hitting “edit” on the entry gives the HomePage.

The cause of the problem is clearly that I had renamed this entry to the (less beautiful but more sane) title Ravenel’s spectrum, leaving but a redirect to “MΩΩSU(n)” there.

So part of the system must know that the entry is gone and redirected. But other part of the system still displays the old version of the entry, without allowing to edit it away!

2. Thanks for raising, I’ll look into it as soon as I can!

• CommentRowNumber106.
• CommentAuthorRichard Williamson
• CommentTimeJan 28th 2021
• (edited Jan 28th 2021)

Re #104: This was a curious one. The problem was that the cache of the beautifully named page was not removed. It turns out that the reason for this was the presence of the unicode character Ω; I could not even remove the cache file manually using rm on the server when using the full file name, I used some unique wildcard specification of it that did not involve a unicode character.

Though some experimentation indicates that only certain unicode characters lead to this issue, and thus its occurrence is not especially likely in general, I have made what I hope is a fix now.

• CommentRowNumber107.
• CommentAuthorUrs
• CommentTimeJan 29th 2021

Thanks!!

• CommentRowNumber108.
• CommentAuthorRichard Williamson
• CommentTimeFeb 3rd 2021
• (edited Feb 3rd 2021)

I have announced it in another thread, but I have now implemented an initial version of a fully fledged referencing mechanism for the nLab, as discussed in #98 - #101. Part of this implementation actually generates more or less exactly the same kind of page as Urs proposed in #101, just not a main nLab page, but a ’special’ page under nlab/reference/show which can be ’included’ using \bibitem rather than !include.

(What was requested in #98 is not implemented yet, just \cite).

• CommentRowNumber109.
• CommentAuthorzskoda
• CommentTimeFeb 4th 2021

There is a bug in referencing passworded pages (private labs). If I have a link from outside of my private lab and click on it during a day in which I did not log previously into the private page it will open the login page instead (OK). Then you enter or click the password (being saved in browser hence automatically entered or not), then it gets into the private lab, but during your fight with login window it lost the information which page was originally supposed to enter and it opens the homepage of the private lab instead. I think the default behavior would be to open the referenced page once the password is given.

Why this matters ? In my experience, it is fairly often time consuming to return to the referencing link and/or find it, for example if you have many windows open, you took a link from one window to open the private page in a new window. Then, after your link is lost in a fight with login window, it is difficult to find which one out of other 10-20 windows or tabs (which you did not plan to return soon to) contained the original link. Or one sometimes manually writes a long link to a private page and the link gets lost.

• CommentRowNumber110.
• CommentAuthorzskoda
• CommentTimeFeb 4th 2021
• (edited Feb 4th 2021)

In edit mode, Hide markup help button has a suboptimal behaviour. People use this button if they want a clean page when editing. They sometimes also want to have wider place for the edit subwindow, but this does not happen. For me, usage of hide button is important when I share screen with somebody in Zoom and explain, say some math, by writing/solving some example in an edit window. After the session I tidy the example and publish it in my personal lab. The usage of $n$Lab window is better than using an external editor as one can use the code which is previously in this scratch page (say the code which is already compiled and checked for rendering). For example of a personal lab page which I created in real time look for stat-041220 (zoranskoda). I spent only 20 minutes to tidy the page after editing it in a live instruction session for my students.

1. If you click on it and save, and reopen, the help will again reappear. If you do 20 saves and edits each time the help will reappear on the right hand side of the browser.

2. When one hides markup help, the space where the help becomes empty, but the window for editing stays shrunk to the previous width. I think that many editing tasks could be performed better in the edit window comprising almost the width of the browser and this is particularly important for readability of long formulas and when you share the screen.

• CommentRowNumber111.
• CommentAuthorvarkor
• CommentTimeFeb 12th 2021

There appears to be a missing space in Lex between “small” and “finitely” in the first bullet point, but there is a space in the source for the page.

• CommentRowNumber112.
• CommentAuthorUrs
• CommentTimeFeb 13th 2021

This is a known bug, whitespace disappears between consecutive hyperlinked words. To work around it, for the moment, I have enforced whitespace (at Lex) by inserting

  $\;$

3. Yes, the problem is that this is a bug in maruku, the Markdown renderer that Instiki uses, rather than in code I have written or in the old Instiki, so is tricky to fix. It will be gone once we move to the new Markdown renderer.

• CommentRowNumber114.
• CommentAuthorMike Shulman
• CommentTimeFeb 14th 2021

The algorithm that associates nForum discussions to nLab pages appears to be at least partially case-insensitive. This leads to, e.g., the “Discuss this page” link from span going to this discussion which is actually about the page Span.

• CommentRowNumber115.
• CommentAuthorTim_Porter
• CommentTimeFeb 23rd 2021
• (edited Feb 23rd 2021)

Trying to correct a typo in higher Atiyah groupoid, pressing submit just gave me the same edit page. (The typo was Setc instead of Sect)

• CommentRowNumber116.
• CommentAuthorRichard Williamson
• CommentTimeFeb 23rd 2021
• (edited Feb 23rd 2021)

Thanks very much for reporting this Tim, the bug in the error handling was introduced in my major (if largely invisible) change announced here. I have now fixed the bug (see github), and also fixed the typo that you wished to fix (and a LaTeX error).

• CommentRowNumber117.
• CommentAuthorRichard Williamson
• CommentTimeFeb 23rd 2021
• (edited Feb 23rd 2021)

Re #114: Thanks for raising! I saw this when you first raised it, but then forgot about it; I have now fixed this. It can be tested for the pages SU(2) and su(2).

I fixed it about a year ago for the edit announcer, but the discussion detector is independent of that. The original reason for case insensitivity was that when these mechanisms were introduced, there was still plenty of inconsistency in titling of nForum discussions vs nLab page titles, and the idea was to avoid overlooking an existing page. Over the years since, things have become much more consistent, and it definitely it is better with case-sensitivity now.

4. A little tweak has now been made to show the wiki name as title of a wiki home page (e.g. ’nLab’ as title of HomePage) rather than the rather ugly ’HomePage’.

• CommentRowNumber119.
• CommentAuthorUrs
• CommentTime6 days ago

An edit I made has crashed the page flavour anomaly, but I can’t figure out what it was!

The error message is::

XML Parsing Error: mismatched tag. Expected: </div>. Location: https://ncatlab.org/nlab/show/flavour+anomaly Line Number 729, Column 35:

5. I’ll take a look later.

• CommentRowNumber121.
• CommentAuthorUrs
• CommentTime6 days ago

I have isolated the problem:

The error appears when an imagefromfile-environment has (a) a caption and (b) is included in a center-environment.

A minimal example is now in the Sandbox (which thereby doesn’t display, at the moment…)

6. I have now fixed this. Now that things work again, I have tweaked the syntax for some of the images at flavour anomaly to use captions correctly. Please check that it looks as intended!

• CommentRowNumber123.
• CommentAuthorUrs
• CommentTime5 days ago

Thanks! Looks good.

• CommentRowNumber124.
• CommentAuthorUrs
• CommentTime5 days ago

Minor point, but there is a grammar glitch in the new instructions on the right of the edit pane, where it says

Tikz can be used for figures almost exactly in LaTeX

(“as in”).

Maybe more importantly, as I was just reminded when I tried – and failed – to find the thread where you announced the renovation of the edit comments:

Search results on the nForum appear in chronological order, but they ought to appear in anti-chronological order (i.e. latest on top).

Moreover, there is only a “Next” button that jumps 20 or so search results ahead.

Together this makes it hard, at the moment, to have a useful search on the nForum for any keyword that has a non-trivial number of hits.