You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've encountered an issue with the neopyter plugin that seems to be related to its cell synchronization mechanism. It appears that the plugin only synchronizes the current cell to improve speed. However, this leads to a problem when the number of cells in a *.ju.py file changes, as the changes are not always synchronized promptly.
For example, when I adjust or delete cells from the bottom, the synchronization does not reflect the changes immediately. I have to enter the 'i' mode to see the updates. Consider the following scenario:
Initial state:
# %%
# something cell1
# %%
# if I delete the above line
# something cell2
# %%
The changes are not synchronized until I enter 'i' mode. @AbaoFromCUG
The text was updated successfully, but these errors were encountered:
After I checked the code, I think we have full sync and partial sync, if we choose to use :Neopyter sync current. we can full sync all the cell. However, I wonder if it's better to check the number of the cell or something to use full sync when it's necessary. At least in my case, the number of the cell might be wrong.
Hi,
I've encountered an issue with the neopyter plugin that seems to be related to its cell synchronization mechanism. It appears that the plugin only synchronizes the current cell to improve speed. However, this leads to a problem when the number of cells in a *.ju.py file changes, as the changes are not always synchronized promptly.
For example, when I adjust or delete cells from the bottom, the synchronization does not reflect the changes immediately. I have to enter the 'i' mode to see the updates. Consider the following scenario:
Initial state:
The changes are not synchronized until I enter 'i' mode.
@AbaoFromCUG
The text was updated successfully, but these errors were encountered: