Open breedx opened 10 years ago
I'm confused. This takes a Markdown editor into a full on Google Docs editor, which is not the purpose of Dillinger.
Yes, exactly. A markdown editor of markdown files on google docs could be classified as a google docs editor. This would give tighter integration to a cloud filesystem which I think it needs. It shouldn't limit it.
well that is not the point of dillinger. Dillinger is a markdown editor not a google docs editor. feel free to fork and have at it!
I'm curious, what is the distinction between files stored on google drive and files stored in local storage. Both are markdown files. What is drawing the line between one side being Dillinger and the other side being 'not'.
Local is localStorage in the browser.
I'd like to see Drive's on line collaborative editing (Many writers at once).
I can very much see the point that @breedx is making. Markdown is markdown. What is the source of the markdown is irrelevant. On the other hand, I am having a lot of trouble with the GD integration. It doesn't see my markdown files, no matter what I press or type - except for one file, which is not the file I want to edit. This file does not contain spaces in its name, as opposed to the other files, which Dillinger is not seeing. Perhaps, this is the reason? In this case, why have Dillinger "guess" at what files I may want to edit, instead of letting me open any file? Maybe, I have markdown in a file without an extension at all, or with an extension that is proprietary to some other tool, but still contains valid classical markdown.
I suggest that Dillinger should allow browsing and searching through all files.
It only searches for files that have the .md or .markdown extension currently. You could submit a pull request if you want to search all files if you like!
On Sun, Oct 2, 2016 at 12:37 PM, XedinUnknown notifications@github.com wrote:
I can very much see the point that @breedx https://github.com/breedx is making. Markdown is markdown. What is the source of the markdown is irrelevant. On the other hand, I am having a lot of trouble with the GD integration. It doesn't see my markdown files, no matter what I press or type - except for one file, which is not the file I want to edit. This file does not contain spaces in its name, as opposed to the other files, which Dillinger is not seeing. Perhaps, this is the reason? In this case, why have Dillinger "guess" at what files I may want to edit, instead of letting me open any file? Maybe, I have markdown in a file without an extension at all, or with an extension that is proprietary to some other tool, but still contains valid classical markdown.
I suggest that Dillinger should allow browsing and searching through all files.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/joemccann/dillinger/issues/238#issuecomment-250980674, or mute the thread https://github.com/notifications/unsubscribe-auth/AAC8auHbPMeLpn-_iiYVT815WRdI7SKQks5qv93QgaJpZM4Cje9G .
@joemccann, I imagine that I would first have to create a separate issue, since this is a bug report: it's not seeing the *.md
files.
As I've mentioned in my original comment,
It doesn't see my markdown files, no matter what I press or type - except for one file, which is not the file I want to edit.
I understand that you cannot reproduce this. But perhaps, I could give you more details about the environent/Drive/something else?
@XedinUnknown try disconnecting and reconnecting to Google Drive as see if that helps. You can also provide a screen capture video
It would be very useful to see the folder structure too. Right now I can't seem to get to the files I want to edit:
It only searches for all .MD files - they should all show up
On Tuesday, June 27, 2017, Roman Random notifications@github.com wrote:
It would be very useful to see the folder structure too. Right now I can't seem to get to the files I want to edit: [image: jun-27-2017 12-00-05] https://user-images.githubusercontent.com/1634044/27582133-31c20db2-5b30-11e7-93e3-fb24f7191232.gif
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/joemccann/dillinger/issues/238#issuecomment-311312965, or mute the thread https://github.com/notifications/unsubscribe-auth/AAC8al2guwRq6g_kABy7Nx9OBajFYfKIks5sINNQgaJpZM4Cje9G .
-- Sent from Joe In Real Life
Unfortunately it doesn't work for me...
What's the name of the file you are searching for? I'll see if I can reproduce it
On Tuesday, June 27, 2017, Roman Random notifications@github.com wrote:
Unfortunately it doesn't work for me...
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/joemccann/dillinger/issues/238#issuecomment-311317793, or mute the thread https://github.com/notifications/unsubscribe-auth/AAC8aiYc6Kkv5Q5DmvJ2J4pdatwwSMeNks5sINhlgaJpZM4Cje9G .
-- Sent from Joe In Real Life
Ableton Live.md or Bash.md
I created a new file, saved it to Google Drive as "Bash.md". Then went to import it and it was there:
Maybe try unlinking and linking your Google Drive with Dillinger?
I tried several times. I put the file in the root folder, in subfolders, with different names and nothing seems to work. But now I noticed that the files that it does find are all from the "Shared with me" folder. So it might be that if results are returned from a shared folder first it doesn't look further into your own folders.
A similar thing happens to me! I have a file in GDrive called Device Inventory.md
and in GDrive the properties clearly indicated it was created with Dillinger. But in Dillinger when I try to Import from Google Drive it doesn't show up!
Sounds like a bug with search.
On Wed, Aug 14, 2019, 8:24 AM Schultzter notifications@github.com wrote:
A similar thing happens to me! I have a file in GDrive called Device Inventory.md and in GDrive the properties clearly indicated it was created with Dillinger. But in Dillinger when I try to Import from Google Drive it doesn't show up!
[image: image] https://user-images.githubusercontent.com/30871/63033534-c9f95800-be85-11e9-8544-e9d729757596.png
[image: image] https://user-images.githubusercontent.com/30871/63033648-fa40f680-be85-11e9-82e4-066ab370b12e.png
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/joemccann/dillinger/issues/238?email_source=notifications&email_token=AAALY2V3DMIUBC7I3ROIV6TQEQPTVA5CNFSM4AUN55DKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4JFBCY#issuecomment-521293963, or mute the thread https://github.com/notifications/unsubscribe-auth/AAALY2WX24IHTEWOKYBKKLTQEQPTVANCNFSM4AUN55DA .
Dillinger is awesome, however the google drive integration is simplistic.
proposed features, i.e. integration with google drive sdk: 'open with' xxx inside of google drive. 'create new with' xxx inside of google drive. association with mime types. periodic saving to drive.
Fork is off of the master.