Home → Problems →

Window size is locked when opening unrecognized file

• Edit

Matthew

17 May, 2012 04:09 PM

If I open a file with an unrecognized format (non-UTF8), a warning is displayed in a window of fixed size. Choosing an alternate stylesheet from the menu at bottom-left allows me to view the parsed document (at least for external parsers - I'm using rST), but I can't resize the window.

I would expect that either (1) I would be prevented from taking any actions on the window (such as choosing a stylesheet) or, preferably, (2) I would be able to resize the window.

-Matthew

1. Support Staff 1 Posted by Brett on 17 May, 2012 04:46 PM

   

   If it's parseable, it should be opening without error. I don't want to make the error nib resizable, I'd rather just avoid showing it in cases where you can actually get a parser working. Can you post a copy of a file that this happens on for testing?

   • Edit

2. Support Staff 2 Posted by Brett on 17 May, 2012 04:48 PM

   

   If it's parseable, it should be opening without error. I don't want to make the error nib resizable, I'd rather just avoid showing it in cases where you can actually get a parser working. Can you post a copy of a file that this happens on for testing?

   • Edit

3. 3 Posted by Matthew on 17 May, 2012 06:52 PM

   

   Hi, Brett. Thanks for the quick reply.

   Here's an example file. It's a mess (that's why I'm working with it), but it is parseable (with errors).

   My custom markdown processor is /opt/local/bin/rst2html-2.7.py from the MacPorts py27-docutils port.

   -Matthew

   • bbpasswdchange.rst 4.12 KB
   • Edit

4. Support Staff 4 Posted by Brett on 17 May, 2012 07:16 PM

   

   Do you know offhand what encoding it's using?

   • Edit

5. 5 Posted by Matthew on 17 May, 2012 07:20 PM

   

   I'm not sure what it was written in originally, but the file command reports:

   bbpasswdchange.rst: Non-ISO extended-ASCII English text

   • Edit

6. Support Staff 6 Posted by Brett on 17 May, 2012 07:39 PM

   

   Is this a common occurrence? That's an encoding that I can't easily account for. Can you just save as UTF-8, or is there an editor that's producing these by default?

   I've fixed it for the next version so that you should never be able to get to the file from the error window, but I can't -- at least for the moment -- find an easy way to handle this encoding.

   • Edit

7. 7 Posted by Matthew on 17 May, 2012 09:11 PM

   

   This is the first time it's happened to me. Apparently that file was created in Notepad++ on Windows. I think your choice of solution is appropriate.

   I'm curious though, why are you checking the encoding at all when an external parser is selected?

   -Matthew

   • Edit

8. Support Staff 8 Posted by Brett on 17 May, 2012 09:26 PM

   

   Because Marked will open _any_ file. If it can't read it as a text file, it has to kick it out. I could see an argument for opening any file when using a custom processor, but the potential reasoning for doing that stretches far beyond Marked's intended purpose, I think.

   • Edit

9. 9 Posted by Matthew on 17 May, 2012 09:51 PM

   

   Ah, that makes complete sense.

   I do notice that file -I <filename> includes a MIME type. For this problematic file, it does report text/plain; charset=unknown-8bit. I'm not sure if you can depend on that text/* for everything you're interested in opening, but it might be an option worth investigating.

   Thanks for talking it over with me, and thanks for Marked.

   -Matthew

   • Edit

10. Support Staff 10 Posted by Brett on 17 May, 2012 09:59 PM

    

    Sure thing.

    MIME (and UTC in general) are entirely unpredictable. I originally thought I could just look for text/plain and public.plain-text, but boy was I wrong :).

    • Edit

11. 11 Posted by John on 23 Jun, 2012 10:55 PM

    

    I'm having a similar problem. However, for me Marked.app seems to think that my .md files are not readable, if they are managed by iCloud, under ~/Library/Mobile Documents (mine are under Byword), as described in another tip here in the support discussions. The only way I can get Marked to properly load my iCloud-managed .md files is to rename them with a .txt extension. Not ideal, as the documentation for Byword states that by default the MarkDown features are only enabled for files with a markdown extension (i.e. .md, .markdown, etc.).

    Also if I have a .md file managed anywhere else on the filesystem, then choose to move them to iCloud, Marked properly detects the move, but (boom) it loses the ability to read them,complaining about the codepage.

    • Edit

12. Support Staff 12 Posted by Brett on 24 Jun, 2012 12:43 AM

    

    When the files are in iCloud, what method are you using to open them?

    -Brett (on iPhone)

    • Edit

13. 13 Posted by John on 25 Jun, 2012 06:28 PM

    

    Sorry for my delay here. Did a bit more testing, and I can't seem to reproduce what I thought I was seeing.

    It seems that the trouble is mainly when moving a document to iCloud, when Marked is viewing it. Marked seems to be aware of the move, but it stops displaying the file, complaining about the codepage, as described earlier.

    If I open the document again, using any means (i.e. File/Open -> ~/Library/Mobile Documents/...byword... , or by dragging the document from there onto Marked.app in the Dock, it seems to pick up again fine.

    I do however have to close the previous window. As Matthew has described, the window size is locked after displaying the codepage error.

    • Edit

14. Support Staff 14 Posted by Brett on 06 Jul, 2012 01:35 PM

    

    I'm not sure why that's happening, but I'll look into it. Due to the way Marked works, it does expect a file to remain stationary while the document is open, and isn't entirely flexible on that. I would like it to be. I'll research a solution for that and any special circumstances surrounding iCloud.

    • Edit