Not signed in

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

• Username
• Password
• Remember me

• Sign in using OpenID
• Remember me

• Forgot your password?
• Apply for membership

2-category 2-category-theory abelian-categories adjoint algebra algebraic algebraic-geometry algebraic-topology analysis analytic-geometry arithmetic arithmetic-geometry book bundles calculus categorical categories category category-theory chern-weil-theory cohesion cohesive-homotopy-type-theory cohomology colimits combinatorics complex complex-geometry computable-mathematics computer-science constructive cosmology definitions deformation-theory descent diagrams differential differential-cohomology differential-equations differential-geometry digraphs duality elliptic-cohomology enriched fibration foundation foundations functional-analysis functor gauge-theory gebra geometric-quantization geometry graph graphs gravity grothendieck group group-theory harmonic-analysis higher higher-algebra higher-category-theory higher-differential-geometry higher-geometry higher-lie-theory higher-topos-theory homological homological-algebra homotopy homotopy-theory homotopy-type-theory index-theory integration integration-theory k-theory lie-theory limits linear linear-algebra locale localization logic mathematics measure-theory modal modal-logic model model-category-theory monad monads monoidal monoidal-category-theory morphism motives motivic-cohomology nforum nlab noncommutative noncommutative-geometry number-theory of operads operator operator-algebra order-theory pages pasting philosophy physics pro-object probability probability-theory quantization quantum quantum-field quantum-field-theory quantum-mechanics quantum-physics quantum-theory question representation representation-theory riemannian-geometry scheme schemes set set-theory sheaf simplicial space spin-geometry stable-homotopy-theory stack string string-theory superalgebra supergeometry svg symplectic-geometry synthetic-differential-geometry terminology theory topology topos topos-theory tqft type type-theory universal variational-calculus

1. • CommentRowNumber1.
   • CommentAuthorTobyBartels
   • CommentTimeMar 24th 2010
   • PermaLink
   Author: TobyBartels
   Format: MarkdownIf you have a page, say [[marked simplicial set]], that you want to get rid of because you have moved all of the material to another page, say [[model structure for Cartesian fibrations]], then it will *not* work to simply add `[[!redirects marked simplicial set]]` to [[model structure for Cartesian fibrations]] and then move [[marked simplicial set]] to [[marked simplicial set > history]] using the all of the automatic features of the page move command. The reason is that, by default, the command `[[!redirects marked simplicial set]]` will be added to [[marked simplicial set > history]] as part of the course of the move. And so all of the links to [[marked simplicial set]] will redirect to [[marked simplicial set > history]], rather than to [[model structure for Cartesian fibrations]] as you wanted. And what's worse, all of the old material will remain on [[marked simplicial set > history]], so readers who get there by mistake may not even realise that something is wrong, unless they look carefully at the page name. The correct thing to do is this: First, start the move from [[marked simplicial set]] to [[marked simplicial set > history]], but *before you Submit* (although after you enter the New name), click in the edit window. This will make `[[!redirects marked simplicial set]]` appear at the top. Delete everything except that line, and change that line to `< [[marked simplicial set]]` (notice that you only have to edit the beginning of the line), or something like that. *Then* Submit. Now the only redirect for [[marked simplicial set]] that exists is the one that you want, to [[model structure for Cartesian fibrations]]. And if anybody does land on [[marked simplicial set > history]] by accident, all that they will see is ‘< [[marked simplicial set]]’, which will automatically take them to whatever the correct redirect target for that may be (currently [[model structure for Cartesian fibrations]], maybe something else if you change it later).

   If you have a page, say marked simplicial set, that you want to get rid of because you have moved all of the material to another page, say model structure for Cartesian fibrations, then it will not work to simply add [[!redirects marked simplicial set]] to model structure for Cartesian fibrations and then move marked simplicial set to marked simplicial set > history using the all of the automatic features of the page move command. The reason is that, by default, the command [[!redirects marked simplicial set]] will be added to marked simplicial set > history as part of the course of the move. And so all of the links to marked simplicial set will redirect to marked simplicial set > history, rather than to model structure for Cartesian fibrations as you wanted. And what's worse, all of the old material will remain on marked simplicial set > history, so readers who get there by mistake may not even realise that something is wrong, unless they look carefully at the page name.

   The correct thing to do is this: First, start the move from marked simplicial set to marked simplicial set > history, but before you Submit (although after you enter the New name), click in the edit window. This will make [[!redirects marked simplicial set]] appear at the top. Delete everything except that line, and change that line to < marked simplicial set (notice that you only have to edit the beginning of the line), or something like that. Then Submit.

   Now the only redirect for marked simplicial set that exists is the one that you want, to model structure for Cartesian fibrations. And if anybody does land on marked simplicial set > history by accident, all that they will see is ‘< marked simplicial set’, which will automatically take them to whatever the correct redirect target for that may be (currently model structure for Cartesian fibrations, maybe something else if you change it later).

2. • CommentRowNumber2.
   • CommentAuthorUrs
   • CommentTimeMar 24th 2010
   • PermaLink
   Author: Urs
   Format: MarkdownThanks, Toby, for the detailed explanation. I wasn't aware of that. I think I fixed it now, following your instructions. So what is that lower-than-command?

   Thanks, Toby, for the detailed explanation. I wasn't aware of that.

   I think I fixed it now, following your instructions.

   So what is that lower-than-command?

3. • CommentRowNumber3.
   • CommentAuthorTobyBartels
   • CommentTimeMar 24th 2010
   • PermaLink
   Author: TobyBartels
   Format: MarkdownThe `&lt;` just makes a little arrow '<'. It is purely cosmetic, to balance the '>' in the archive page name. (You have to write `&lt;` instead of `<` to avoid confusing the parser.) Then the link is there in case somebody gets lost. I've written some general instructions at [HowTo#merging](http://ncatlab.org/nlab/show/HowTo#merging).

   The < just makes a little arrow '<'. It is purely cosmetic, to balance the '>' in the archive page name. (You have to write < instead of < to avoid confusing the parser.) Then the link is there in case somebody gets lost.

   I've written some general instructions at HowTo#merging.