Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Config Question #1

Closed
evanricard opened this issue Sep 26, 2019 · 4 comments
Closed

Config Question #1

evanricard opened this issue Sep 26, 2019 · 4 comments
Assignees
Labels
good first issue Good for newcomers

Comments

@evanricard
Copy link

image

Hey Bantya, I am unsure what I'm doing wrong...I've got the necessary fields populated on the right hand side for the writable config file. Thanks!

@bantya
Copy link
Owner

bantya commented Oct 18, 2019

@evanricard, I can't understand your problem. Can you please elaborate? Please provide steps to replicate your issue. 😀

And, sorry for late reply. 😒

@bantya bantya added good first issue Good for newcomers help wanted Extra attention is needed question Further information is requested config-related The issue is regarding config file. and removed help wanted Extra attention is needed labels Oct 18, 2019
@evanricard
Copy link
Author

evanricard commented Oct 18, 2019

No problem @bantya, looking back at this...I can't quite understand it myself sorry I should have clarified. I am trying to filter keypirinha when I want to do a search through zeal for a specific data type or object that I might need to know about at any given time for programming. Specifically, I was trying to configure your package so I basically copied the read-only version of the configuration file, uncommented the text, and then pasted into the writable config, zealous.ini.

Unfortunately, typing in a filter like net: for the .NET framework just prompts me to refresh your package and does not resolve to Zeal like I was hoping. Anyways, thanks!

image

@bantya bantya pinned this issue Dec 13, 2019
@bantya bantya self-assigned this Dec 13, 2019
@bantya
Copy link
Owner

bantya commented Dec 13, 2019

I have a solution for you.

Looks like you did everything right but went wrong in case of Zeal Doc Name. As per the first screenshot you attached, your zealous.ini file is as:

[main]
# Plugin's main configuration section
#
# * path
#   The path to the zeal executable.
path = "C:\Program Files\Zeal"
#
# * docset_path
#   The zeal docsets path.
docset_path = "C:\Users\evanricard\AppData\Local\Zeal\Zeal\docsets"
#
# * results
#   The total results count.
result = 15

[docs]
# The zeal docs list
#
# Syntax:
#   [distinct keyword] = [zeal doc name]
#
# Examples:
#   ap = apache
#   ng = nginx
net = .NET
js = Javascript

The culprit here in [docs] section in entry net = .NET (also in js = Javascript). For the .NET Framework, the zeal doc identifier is net (NOT .NET).

Now you may ask, how on earth should I decide what to use? Good question!

Here is the paragraph where I apologize 😖 for not being clear about what zeal doc identifier to use and where to find it. The documentation fell short here.

Now to find appropriate doc identifier follow mentioned steps 🐾:

  1. You should go to zeal docs folder (docset_path in [main] section) i.e. C:\Users\USERNAME\AppData\Local\Zeal\Zeal\docsets (in your case: C:\Users\evanricard\AppData\Local\Zeal\Zeal\docsets). Here you will find all of your installed docsets as:

    image

  2. Open your desired docset folder (in your case: NET_Framework.docset)

  3. Go to Contents folder.
    Here you will find Info.plist file. Open this file in your code editor (or Notepad will do). You will see something like:

    image

  4. The Info.plist is an XML file. Look for key CFBundleIdentifier. Copy the adjacent string value (in your case: net NOT .NET).
    If by chance CFBundleIdentifier is not present (highly unlikely!), look for DocSetPlatformFamily and copy it's value.

So now you can find the exact zeal docs identifier for your docset.

NOTE: The identifiers have to be exactly same as given in Info.plist file. Case must be same. That's why I formerly said js = Javascript is also a culprit. So, your [docs] section should be like:

[docs]
# The zeal docs list
#
# Syntax:
#   [distinct keyword] = [zeal doc name]
#
# Examples:
#   ap = apache
#   ng = nginx
net = net
js = javascript

Hope this lengthy late reply solved your problem! If problem persists, consult your family doctor 😁.

🙏🏼

@bantya
Copy link
Owner

bantya commented Dec 13, 2019

So I am considering it as solved and closing it!

@evanricard If you want any help again, please let me know here and I will re-open this if required!

🙏🏼

@bantya bantya closed this as completed Dec 13, 2019
@bantya bantya added the update-readme Update the README file label Dec 13, 2019
bantya added a commit that referenced this issue Dec 13, 2019
@bantya bantya removed config-related The issue is regarding config file. question Further information is requested update-readme Update the README file labels Dec 13, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

2 participants