[Bug 25830]
(In reply to Stewart Gordon from [comment #218](https://bugzilla.mozilla.org/show_bug.cgi?id=57342#c218)) I think you completely misunderstood what I was getting at, because your final statement is what I was saying (well attempting to as it obviously wasn't as clear as I hoped). All I was saying is that if a file is identified with a mime type of `text/*` that it is text, and firefox displays text just fine as it currently does with `text/plain`. So firefox can handle any text file it doesn't explicitly have another process for as `text/plain` to display it **in Firefox**, and that should be an option in addition to _save_, and _specifying an external application_ for handling that file. I was not requesting that the user choose on an all-or-nothing basis at all, I wanted to add an option that doesn't exist at this time, but should for text/* types because the support is already baked in. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/25830 Title: Option to display file in browser, treat as text/plain To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/25830/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25830]
Addressing this issue would help a lot of power users. I think all that's needed is the capability to set somewhere (even about:config) that all unknown text/* types should be handled as internally as text/plain. Currently I have to use Chrome w/ an extension to render a markdown file from my local filesystem. It is loaded w/ the appropriate mime type: text/markdown which according to this stackoverflow (https://stackoverflow.com/questions/10701983/what-is-the-mime-type-for- markdown) was registered as RFC7763 in March of 2016. There is at least one firefox extension which will render a markdown file. but it never gets that far, firefox only gives the options to download or to specify an external application for the file. There are other text/* types that it would be really nice if they were just viewable in the browser rendered as text/plain, such as those for source files (text/x-c, text/x-java-source, ...). On my system the mime type is also associated w/ the list of applications I select from in the file manager to open those files, so I want to be able to distinguish them from one another (I want to open markdown files with different applications than js source files or script files for example). I mention this because one workaround suggested was just to tag markdown files as text/plain, but I'd rather continue to use Chrome than lose the ability to distinguish the files in the file manager. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/25830 Title: Option to display file in browser, treat as text/plain To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/25830/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 718160] [NEW] Installer crashed
Public bug reported: Binary package hint: ubiquity I was actually installing Linux Mint 9 KDE amd64, but the crash requested it be reported here. Traceback (most recent call last): File /usr/lib/ubiquity/bin/ubiquity, line 524, in module main(oem_config) File /usr/lib/ubiquity/bin/ubiquity, line 509, in main install(args[0], query=options.query) File /usr/lib/ubiquity/bin/ubiquity, line 242, in install ret = wizard.run() File /usr/lib/ubiquity/ubiquity/frontend/kde_ui.py, line 460, in run self.progress_loop() File /usr/lib/ubiquity/ubiquity/frontend/kde_ui.py, line 863, in progress_loop (ret, realtb)) RuntimeError: Install failed with exit code 1 Traceback (most recent call last): File /usr/share/ubiquity/install.py, line 2566, in module install.run() File /usr/share/ubiquity/install.py, line 388, in run self.configure_plugins() File /usr/share/ubiquity/install.py, line 1088, in configure_plugins raise InstallStepError(Plugin %s failed with code %s % (plugin.NAME, ret)) InstallStepError: Plugin usersetup failed with code 135 ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/718160 Title: Installer crashed -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 718160] Re: Installer crashed
** Attachment added: partman https://bugs.launchpad.net/bugs/718160/+attachment/1847252/+files/partman -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/718160 Title: Installer crashed -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 718160] Re: Installer crashed
Not sure why I couldn't attach 2 files when I filed the bug, but here's the syslog ** Attachment added: syslog https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/718160/+attachment/1847253/+files/syslog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/718160 Title: Installer crashed -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 718160] Re: Installer crashed
You may be able to ignore this bug. When I rebooted I got a SMART error on the drive, so the problem may just be a bad hard drive. Since it was a relatively new computer (I got it in Oct 2010) and Win 7 has been running fine, I didn't suspect a bad drive until I saw that S.M.A.R.T. error on the BIOS POST. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/718160 Title: Installer crashed -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
