Stories
Slash Boxes
Comments

SoylentNews is people

Community Reviews

Hands on With System76’s Beautiful Linux Distro Pop!_OS

posted by Fnord666 on Monday January 15 2018, @08:26PM   Printer-friendly
from the It's-FOSS dept.

Phillip writes:

Linux system manufacturer System76 introduced a beautiful looking Linux distribution called Pop!_OS. But is Pop OS worth an install? Read the Pop OS review and find out yourself.

More at : https://itsfoss.com/pop-os-linux-review/

Original Submission

 
This discussion has been archived. No new comments can be posted.
Hands on With System76’s Beautiful Linux Distro Pop!_OS | Log In/Create an Account | Top | 127 comments | Search Discussion
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

  • (Score: 2) by hendrikboom on Wednesday January 17 2018, @03:46AM (4 children)

    by hendrikboom (1125) Subscriber Badge on Wednesday January 17 2018, @03:46AM (#623419) Homepage Journal

    How compatible is Zim with revision control? Most word processor file formats are terrible for it. A merge is a calamity.

    Starting Score:    1  point
    Karma-Bonus Modifier   +1  
    Total Score:   2  

  • (Score: 2) by Marand on Wednesday January 17 2018, @04:23AM

    by Marand (1081) on Wednesday January 17 2018, @04:23AM (#623440) Journal

    Zim notebooks consist of plain text files (.txt extension), with sub-pages stored in subdirectories. So, say you have a TODO page, and beneath that, "Work" and "Hhome" pages. On the filesystem you'll have "TODO.txt", "TODO/Work.txt" and "TODO/Home.txt", with each file being human-readable. Zim files have a 3 line header, similar to HTTP headers with three entries: Content-Type, Wiki-Format, and Creation-Date. After that is the file body, which is plaintext human-readable conventions for formatting, as documented here [zim-wiki.org] and also available within Zim itself.

    Which is to say, it's very amenable to version control systems because it's all plaintext. The only exception is, if you choose to attach a binary file to a page (either by adding an image to a page or using the "attach external file" option), you get the usual caveats with binary files and VCS. That and the general human-readability of it make it appealing to me, because I hate locking important info into non-standard formats. If Zim ever breaks or stops being maintained, my data is still readable, and it should be simple enough to make a parser for it if I ever need. :D

  • (Score: 2) by Marand on Wednesday January 17 2018, @04:25AM (2 children)

    by Marand (1081) on Wednesday January 17 2018, @04:25AM (#623441) Journal

    Double post because I just noticed after submitting that Zim itself ships with a version control plugin [zim-wiki.org] if you want to automate the process. That page also says basically what I did, and I could have saved myself some typing if I had known about it before posting.

    • (Score: 2) by Gaaark on Thursday January 25 2018, @12:06AM (1 child)

      by Gaaark (41) on Thursday January 25 2018, @12:06AM (#627469) Journal

      I'll answer through to you THIS way: (my zim came with the version control already in action).

      I'm using zim now: VERY NICE! Thanks for the info!

      --
      --- Please remind me if I haven't been civil to you: I'm channeling MDC. ---Gaaark 2.0 ---

      • (Score: 2) by Marand on Thursday January 25 2018, @10:01AM

        by Marand (1081) on Thursday January 25 2018, @10:01AM (#627614) Journal

        Awesome, glad to hear it's working out for you. :D

        It's amazing how useful it can be considering how simple the concept and execution is. Doesn't try to be super fancy, which I think works in its favour, at least for me.