Top 5 Roam Alternatives

< Next Topic | Back to topic list | Previous Topic >

Posted by Darren McDonald
Aug 27, 2021 at 10:34 AM

@Luhmann, I was actually working with Logseq today and discovered the problem is not just with Dropbox.

Basically, when I change the name of a page using “rename” in the pull-down menu, it creates a new page and leaves the old page intact. You only discover this when you view “all pages” to see the list of pages. This results in a long list of unwanted pages and gets rather confusing.

Also, when I delete unwanted pages from a Roam JSON package that I imported into Logseq, the pages reappear when I open Logseq on my iMac at home. I made sure to sync and close Logseq before logging off and opening Logseq on another computer. I am using the Mac desktop version. I tried the online version using my space on Github (repository). The issues with an imported Roam JSON package are worse with the Github repository. This time all the files disappear when Logseq syncs.

So my biggest issues are with pages I made in a fresh new graph (repository) and also when importing a Roam JSON package. I hope I am making sense. I am neither a programmer nor a technical expert when it comes to computer software. I could be doing something wrong, but I don’t know what to do to find out. Any clues? Should I post this to the Logseq forum?

Luhmann wrote:
What is the issue you have with Dropbox? I know a lot of people are
>using it with Dropbox…
> >Darren McDonald wrote:
> >>I find that the major issue I have with the Logseq is using it for a
>>depository with Dropbox which is accessed from the home and work
>>computers. I am sure this will be rectified with time.
>

Posted by Luhmann
Aug 27, 2021 at 10:39 AM

Seems something isn’t right. Should post this in the forum, or for a quicker response perhaps in the official Discord channel. As far as the deleted pages showing up on the other computer - you probably need to do a re-index (from the drop down menu) to get the iMac to register the changes. The last update greatly sped up re-indexing so that should help, but the need to occasionally re-index changes from another computer will probably persist until they offer their own paid sync solution (as Obsidian has done).

Darren McDonald wrote:
@Luhmann, I was actually working with Logseq today and discovered the
>problem is not just with Dropbox.
> >Basically, when I change the name of a page using “rename” in the
>pull-down menu, it creates a new page and leaves the old page intact.
>You only discover this when you view “all pages” to see the list of
>pages. This results in a long list of unwanted pages and gets rather
>confusing.
> >Also, when I delete unwanted pages from a Roam JSON package that I
>imported into Logseq, the pages reappear when I open Logseq on my iMac
>at home. I made sure to sync and close Logseq before logging off and
>opening Logseq on another computer. I am using the Mac desktop version.
>I tried the online version using my space on Github (repository). The
>issues with an imported Roam JSON package are worse with the Github
>repository. This time all the files disappear when Logseq syncs.
> >So my biggest issues are with pages I made in a fresh new graph
>(repository) and also when importing a Roam JSON package. I hope I am
>making sense. I am neither a programmer nor a technical expert when it
>comes to computer software. I could be doing something wrong, but I
>don’t know what to do to find out. Any clues? Should I post this to the
>Logseq forum?
>

Posted by Darren McDonald
Aug 27, 2021 at 10:54 AM

Thanks for the advice, @Luhmann. I see that you are also active on the forum at Logseq offering really useful tips and troubleshooting. Great to know I am amongst such awesomeness! :)
Luhmann wrote:
Seems something isn’t right. Should post this in the forum, or for a
>quicker response perhaps in the official Discord channel. As far as the
>deleted pages showing up on the other computer - you probably need to do
>a re-index (from the drop down menu) to get the iMac to register the
>changes. The last update greatly sped up re-indexing so that should
>help, but the need to occasionally re-index changes from another
>computer will probably persist until they offer their own paid sync
>solution (as Obsidian has done).
> >Darren McDonald wrote:
>@Luhmann, I was actually working with Logseq today and discovered the
>>problem is not just with Dropbox.
>>
>>Basically, when I change the name of a page using “rename” in the
>>pull-down menu, it creates a new page and leaves the old page intact.
>>You only discover this when you view “all pages” to see the list of
>>pages. This results in a long list of unwanted pages and gets rather
>>confusing.
>>
>>Also, when I delete unwanted pages from a Roam JSON package that I
>>imported into Logseq, the pages reappear when I open Logseq on my iMac
>>at home. I made sure to sync and close Logseq before logging off and
>>opening Logseq on another computer. I am using the Mac desktop version.
>>I tried the online version using my space on Github (repository). The
>>issues with an imported Roam JSON package are worse with the Github
>>repository. This time all the files disappear when Logseq syncs.
>>
>>So my biggest issues are with pages I made in a fresh new graph
>>(repository) and also when importing a Roam JSON package. I hope I am
>>making sense. I am neither a programmer nor a technical expert when it
>>comes to computer software. I could be doing something wrong, but I
>>don’t know what to do to find out. Any clues? Should I post this to the
>>Logseq forum?
>>
>

Posted by Luhmann
Aug 27, 2021 at 02:32 PM

After having put my whole life into Logseq, I am very eager to see it survive! But I don’t think I need to worry, the developers are moving very quickly. The latest version might even address the issue I raised above? “File changes from the disk are not refreshed immediately in logseq” is marked as “fixed”... You might want to test it again to see if sync works better now?

Posted by Darren McDonald
Aug 28, 2021 at 02:03 PM

Indeed, the developers certainly move fast! The latest update came through this morning when I started up the app (version 0.3.5) and the issue is now fixed! :) I was toying with Logseq all day today, getting a lot of work done in preparation for fieldwork.

I have a lot of suggestions for new features and improvements on existing features. Most of what I want to suggest already seems to have been submitted by other folks. For instance, the new feature request for a sidebar https://discuss.logseq.com/t/content-bar-on-left-side-and-page-breadcrumbs-on-top/121

I am also trying set up my Zotero account within Logseq. But as of yet, I am have been unable to find a step-by-step guide in how to obtain the necessary information from Zotero to input into Loseq. Do you have any guidance in this area @Luhmann?

Great to see the Discord community so active and helping. Though I am new to Discord and I am having a really difficult time trying to follow the discussion. I much prefer the format on the Logseq Forum.

Anyway, back to work! :)

Cheers! :)

Luhmann wrote:
After having put my whole life into Logseq, I am very eager to see it
>survive! But I don’t think I need to worry, the developers are moving
>very quickly. The latest version might even address the issue I raised
>above? “File changes from the disk are not refreshed immediately in
>logseq” is marked as “fixed”... You might want to test it again to see
>if sync works better now?

Pages: ‹ First < 3 4 5 6 7 8 9 10 >

Back to topic list