« first day (653 days earlier)      last day (1059 days later) » 

3:53 PM
@WeiZhong I think that searches with $\aleph_1$ are good example of situation where searching for arbitrary variables instead of the ones given in the query does not work well. AFAIK the letter $\aleph$ is hardly ever used in mathematics for anything else rather than for cardinals. In Approach0 things like $T_1$, $U_1$, $x_1$ are matches too. Is there some way around this? (If this will need longer explanation, feel free to respond in chat.) — Martin Sleziak 11 secs ago
Let us take this query as an example. It searches for $\mathfrak c$, $\aleph_1$.
The second result I get is this question, which was returned probably because it contains $U_1$.
In this case google would be more useful for me.
Is there way to tell Aproach0 something like: for this particular query do not treat $\aleph$ as a variable but rather as an exact string.
Entering "aleph 1" seems like an reasonable attempt: approach0.xyz/search/?q=%22aleph%201%22&p=1
But still it would be nice to be able to search for something like $\aleph_1=2^x$, where $x$ can be any variable, but $\aleph$ will always be $\aleph$.
BTW the documentation is much more detailed then when we last talked in chat. Good job!
 

« first day (653 days earlier)      last day (1059 days later) »