René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"[Bug]: Should Axes.set_xlim(..., emit=False) really not sync shared axes?","articleBody":"### Bug summary\n\nCurrently, calling `ax.set_xlim(..., emit=False)` explicitly does not sync the xlims to other axes that are sharex with ax (i.e. the other axes keep their previous limits).  This isn't really an accident of implementation, but is rather explicitly implemented at the bottom of Axis._set_lim.\r\n\r\nHowever, this leads to buggy behavior, e.g. tick locators, which are shared between sharex axes, mis-handled being simultaneously assigned to two axes with different limits.\n\n### Code for reproduction\n\n```python\nfig, axs = subplots(1, 2, sharex=True); axs[0].set_xlim((0, .1), emit=False)\n```\n\n\n### Actual outcome\n\n![test](https://github.com/matplotlib/matplotlib/assets/1322974/f0e0b0e7-0df4-47e8-8115-93ab6b9f8357)\r\nNote the nonsensical ticks on the second axis, which still have limits of (0, 1) but uses a tick locator which thinks the limits are (0, 0.1).\n\n### Expected outcome\n\nProbably syncing with sharex axes should always be done, even when emit=False.\n\n### Additional information\n\n_No response_\n\n### Operating system\n\n_No response_\n\n### Matplotlib Version\n\n3.8.0.dev1236+gfc350ea534\n\n### Matplotlib Backend\n\nany\n\n### Python version\n\n3.11\n\n### Jupyter version\n\n_No response_\n\n### Installation\n\ngit checkout","author":{"url":"https://github.com/anntzer","@type":"Person","name":"anntzer"},"datePublished":"2023-06-07T17:07:42.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/26085/matplotlib/issues/26085"}