Jump to content

manahga

Level 1
  • Content Count

    3
  • Joined

  • Last visited

Community Reputation

2 Neutral

About manahga

  1. I would like to propose some enhancements to the ENScript utility provided with the Windows Evernote client. Support for the listing of notebooks beyond just "synced" and "local". Why can't we see a listing of our linked/joined notebooks? Support for creating/importing notes in linked/joined notebooks we have editing privileges to. Is there a reason support is not there for this now? Support for deletion of notes from notebooks you own or have editing privileges to. I know I have seen requests on this before. I realize there are sticky points to this. Especially seeing as there are no unique constraints on note titles. It would be nice to be able to tell the difference between a true empty resultset and an error when exporting using ENScript. For example, when exporting from a specific notebook, I cannot tell the difference when the notebook doesn't exist or doesn't contain any notes. They both return an exit code of 1 and no data.
  2. I would like to propose the updating of the ENScript utility on windows for the following: Allow for the listing of notebooks other than just "sync" and "local. For instance, why can we not see a listing of our joined/linked notebooks? Allow for the importing of notes into linked/joined notebooks for which we have the appropriate edit privileges for. Allow for the deleting of notes from notebooks we own or have access to. I realize there are some sticky points to this in that there are no unique title restrictions on notes. However, this is a sorely missed feature for power users wishing to automate EN through ENScript. When exporting, it would be nice to know the difference between a true error, and just and empty result set. For instance, when attempting to export from a specific notebook that doesn't exist, I would expect that to be an error. However, if the notebook exists, but is empty, IMO this shouldn't be an error. Currently, there is no way to tell the difference as both scenarios return an exit code of 1 and no data. Other related updates: In light of the suggestions above in regard to linked/joined notebooks. I would recommend enforcing unique notebook name constraints across all notebooks. Currently, a linked/joined notebook and a synced/local notebook can exist with the same name.
×
×
  • Create New...