Jump to content

Jakub Sypiański

Member
  • Content Count

    40
  • Joined

  • Last visited

Posts posted by Jakub Sypiański


  1. Thank you for your comments, it makes sense. However, I use Bépo–⌘Qwery, so ⌘V is exactly where it should be (even though V is on a different key). It works for normal copy-paste and it works as expected. The only problem is with Alfred's snippets. I need each time to temporarily switch the layout, get the snippet and revert to Bépo...

     

    In the "Dvorak ⌘Qwerty" layout everything works as expected, including the snippets.

     

    Let's see what the team say.

     

    (As for the formatting, I have no idea why my comments appeared formatted initially.)


  2. Thank you! I'll try to do my best.

    It's the snippets that don't work with Bépo. They work correctly with Dvorak and Qwerty. In case of Bépo the keyword does disappear, but the snippet doesn't reappear.

    Keyboard shortcuts in workflows work correctly and according to the Bépo layout.

    What further information can I provide you with?


  3. @Gareth I don't like the way you present your arguments (also, you have no data to claim that people don't want themes, do you?), but you have a good point: the statistics of active browser users are potentially strongly biased. The impossibility to use the browser of choice due to Alfred's limitations definitely influences statistics. It would be interesting to find out which browsers Alfred users USE, but which they WOULD LIKE to use. However, I don't think that "Firefox: 5%" would suddenly become "People who'd love to use Firefox, but can't: 25%". Just because of the bookmarks?

     

    @deanishe Thank you for the answer. I can't wait to learn to make my own workflows, especially after discovering how supportive and dynamic is the the community here. But for now, I will try to forget how great it would be to have my Vivaldi bookmarks accessible through Alfred. ;)


  4. After updating to Alfred 4, Searchio stopped working. 😱 Below is the log I get. I suppose one has to replace "Alfred 3" with "Alfred 4" or something similar, but I have no idea where. Searchio and Alfred are both up do date.

    [14:57:29.065] Logging Started...
    [14:57:34.577] Searchio![Script Filter] Queuing argument 't'
    [14:57:34.657] Searchio![Script Filter] Queuing argument 'te'
    [14:57:34.684] Searchio![Script Filter] Script with argument 't' finished
    [14:57:34.689] ERROR: Searchio![Script Filter] Code 1: 🍺
    14:57:34 workflow.go:304: --------- Searchio!/2.0.1 (AwGo/0.14.0) ----------
    14:57:34 search.go:127: loading search from /Users/jakub/Library/Application Support/Alfred/Workflow Data/net.deanishe.alfred-searchio/searches/wikipedia-en.json ...
    14:57:34 feedback.go:453: Sent 1 result(s) to Alfred
    14:57:34 workflow.go:352: [ERROR] open /Users/jakub/Library/Application Support/Alfred/Workflow Data/net.deanishe.alfred-searchio/searches/wikipedia-en.json: no such file or directory
    14:57:34 workflow.go:380: ------------------- 3.613668ms -------------------
    [14:57:34.738] Searchio![Script Filter] {
      "variables": {
        "AW_SESSION_ID": "F6ZR89F1TSRJPI272M5P96Z4"
      },
      "items": [
        {
          "title": "open /Users/jakub/Library/Application Support/Alfred/Workflow Data/net.deanishe.alfred-searchio/searches/wikipedia-en.json: no such file or directory",
          "valid": false,
          "icon": {
            "path": "/System/Library/CoreServices/CoreTypes.bundle/Contents/Resources/AlertStopIcon.icns"
          }
        }
      ]
    }
    [14:57:34.758] Searchio![Script Filter] Queuing argument 'tes'
    [14:57:34.788] Searchio![Script Filter] Script with argument 'te' finished
    [14:57:34.796] ERROR: Searchio![Script Filter] Code 1: 🍺
    14:57:34 workflow.go:304: --------- Searchio!/2.0.1 (AwGo/0.14.0) ----------
    14:57:34 search.go:127: loading search from /Users/jakub/Library/Application Support/Alfred/Workflow Data/net.deanishe.alfred-searchio/searches/wikipedia-en.json ...
    14:57:34 feedback.go:453: Sent 1 result(s) to Alfred
    14:57:34 workflow.go:352: [ERROR] open /Users/jakub/Library/Application Support/Alfred/Workflow Data/net.deanishe.alfred-searchio/searches/wikipedia-en.json: no such file or directory
    14:57:34 workflow.go:380: ------------------- 1.294646ms -------------------
    [14:57:34.799] Searchio![Script Filter] {
      "variables": {
        "AW_SESSION_ID": "QSDKE4EPA5JBFFZZSPOU4YMQ"
      },
      "items": [
        {
          "title": "open /Users/jakub/Library/Application Support/Alfred/Workflow Data/net.deanishe.alfred-searchio/searches/wikipedia-en.json: no such file or directory",
          "valid": false,
          "icon": {
            "path": "/System/Library/CoreServices/CoreTypes.bundle/Contents/Resources/AlertStopIcon.icns"
          }
        }
      ]
    }
    [14:57:34.840] Searchio![Script Filter] Queuing argument 'test'
    [14:57:34.888] Searchio![Script Filter] Script with argument 'tes' finished
    [14:57:34.897] ERROR: Searchio![Script Filter] Code 1: 🍺
    14:57:34 workflow.go:304: --------- Searchio!/2.0.1 (AwGo/0.14.0) ----------
    14:57:34 search.go:127: loading search from /Users/jakub/Library/Application Support/Alfred/Workflow Data/net.deanishe.alfred-searchio/searches/wikipedia-en.json ...
    14:57:34 feedback.go:453: Sent 1 result(s) to Alfred
    14:57:34 workflow.go:352: [ERROR] open /Users/jakub/Library/Application Support/Alfred/Workflow Data/net.deanishe.alfred-searchio/searches/wikipedia-en.json: no such file or directory
    14:57:34 workflow.go:380: ------------------- 869.835µs -------------------
    [14:57:34.900] Searchio![Script Filter] {
      "variables": {
        "AW_SESSION_ID": "F6ZR89F1TSRJPI272M5P96Z4"
      },
      "items": [
        {
          "title": "open /Users/jakub/Library/Application Support/Alfred/Workflow Data/net.deanishe.alfred-searchio/searches/wikipedia-en.json: no such file or directory",
          "valid": false,
          "icon": {
            "path": "/System/Library/CoreServices/CoreTypes.bundle/Contents/Resources/AlertStopIcon.icns"
          }
        }
      ]
    }
    [14:57:34.981] Searchio![Script Filter] Script with argument 'test' finished
    [14:57:34.993] ERROR: Searchio![Script Filter] Code 1: 🍺
    14:57:34 workflow.go:304: --------- Searchio!/2.0.1 (AwGo/0.14.0) ----------
    14:57:34 search.go:127: loading search from /Users/jakub/Library/Application Support/Alfred/Workflow Data/net.deanishe.alfred-searchio/searches/wikipedia-en.json ...
    14:57:34 feedback.go:453: Sent 1 result(s) to Alfred
    14:57:34 workflow.go:352: [ERROR] open /Users/jakub/Library/Application Support/Alfred/Workflow Data/net.deanishe.alfred-searchio/searches/wikipedia-en.json: no such file or directory
    14:57:34 workflow.go:380: ------------------- 1.087016ms -------------------
    [14:57:34.996] Searchio![Script Filter] {
      "variables": {
        "AW_SESSION_ID": "QSDKE4EPA5JBFFZZSPOU4YMQ"
      },
      "items": [
        {
          "title": "open /Users/jakub/Library/Application Support/Alfred/Workflow Data/net.deanishe.alfred-searchio/searches/wikipedia-en.json: no such file or directory",
          "valid": false,
          "icon": {
            "path": "/System/Library/CoreServices/CoreTypes.bundle/Contents/Resources/AlertStopIcon.icns"
          }
        }
      ]
    }

     


  5. @vitor

    The thing is that if this feature is implemented as requiring a very specific first character of the suffix (for example "\" or a double space which, I would still argue, people don't normally use in Alfred's window), nothing special will happen to the behaviour of other workflows or features. Unless the user does render them incompatible, but this can always happen anyway. Or are you trying to tell me that Alfred will not be able to await special orders and monitor whatever is typed in its window after we are past the first few letters? In any case, if you don't feel like it, you don't need to continue convincing me, I acknowledge that I'm the only one wanting suffixes, so I will try to focus on alternative solutions. Speaking of which:

     

    @deanishe

    1. Thank you for the suggestion, I will try to learn how to make a workflow out of these exported web searches.

    2. Thank you even more for making a workflow for me. Alas, I get 404 (and a spoon).


  6. I have the impression that the problems you evoke indeed don't apply to web searches, so perhaps allowing OPTIONAL suffixes in this case won't cause problem?

     

    On 5/28/2019 at 12:17 AM, deanishe said:

    FWIW, your suffix-keyword-based websearch could be implemented as a workflow.

     

    I will try to create one, thank you for the tip. But is there a way to somehow export my 250+ web searches?


  7. My sincere thanks. I am learning a lot about how Alfred works from your replies. However, I still have an impression that if Alfred allowed prefixes to be turned on in individual workflows, it would not interfere with other workflows, unless the user makes it interfere.

     

    Actually, I don't have a Workflow. I just have these 250+ Web Searches in the relevant tab of Alfred settings. I will think if I am able to transform these into a workflow (but I don't even see an option in Alfred to copy or export these searches). If it wasn't clear already, I don't know anything about coding and the technology behind Alfred.

     

    The attached screenshot shows what I mean by "cycling": the possibility to type ;a and to see all my prefixes starting with ;a. It seems to me that it's a behaviour that cannot be replicated otherwise. But perhaps I'm wrong?

    Zrzut ekranu 2019-05-25 o 20.19.23.png


  8. You have good arguments for not using such optional suffixes. But you have only one good argument for not implementing such optional suffixes: lack of interest. It’s not worth it to spend time on a feature that won’t be used by many. However, I would argue that a thread such as this is not representative. People may not even realise this feature is possibly useful. We are very much used to prefixes as keywords. On the other hand, perhaps it wouldn’t be very difficult to implement? I have no idea.

     

    @vitor

    1. Thank you for the workflow. Indeed I didn’t realise that it would work that way. I will use your workflow, but it doesn’t solve the crucial issue: I cannot cycle through all my keywords that way (and memorising all 250+ of them it's just not worth it). This would be possible only with suffixes.

    2. As we both now these interfering keywords are easily avoidable by the use of non-word keywords. One general solution would be to require a double space before the keyword. Fast to type and efficient. Anyway, such prefixes would be optional.


  9. I am a bit disappointed by your suggestions but thank you anyway. I already make use of the keyboard shortcuts you mention. But if I didn’t consider it a problem, I would not have asked about the possibility.

     

    I use Web Searches for 184 dictionaries, 34 library catalogues, 11 research tools as well as other things. To this can be added several workflows that are based on search queries. It means that I use Alfred searches in my research several hundred times a day. A huge proportion of this searches is performed through invoking Alfred, returning to the beginning of the line and changing the prefix. This in itself is enough for me to advocate for implementing the optional suffix-model.

     

    The suffix-model would allow not only to modify the search keyword more quickly but also to be able to use all the suggestions. Example: my prefixes for dictionaries are coded as `{;}{first letter of language 1}{first letter of language 2}{first letter fo dictionary’s name}`. For instance: `;aew` for Arabic–English WordReference. It allows me to first choose the language pair and then cycle through all available dictionaries. Now, having suffixes would allow me to use this extremely helpful cycling feature also while the word is already in Alfred search box. Believe me, I never choose a dictionary BEFORE knowing what word I want to look up.

     

    Moreover, having suffixes would allow having a global keyboard shortcut for taking the text selected in Alfred and then choosing what to do with it, while taking advantage of keyword cycling and their easy replacement. 

     

     
     
     
    On 5/24/2019 at 1:04 PM, deanishe said:

    If I want to search Google for “world map”, I’m going to start seeing a load of search results for “world” from the workflow whose keyword is “map”, which isn’t what I want at all.

     

    This is exacerbated by the fact that a lot of workflows/users have one-letter keywords.

     

    My prefixes always start with a special sign (for example `;` for dictionaries), so this problem can hardly ever occur. And one's keywords are all one letter, no problem, I propose this as an optional feature.

     

    17 hours ago, deanishe said:

    If sending the same query to different workflows is something you do a lot, why not implement a Hotkey that simulates ⌘←, ⌥⌦? That should cover the majority of cases.

     

    Unfortunately, not possible, because my keywords have between two and five letters and I don't feel like making them all five letter.  


  10. To search something in Alfred, either through "Web search" or using workflows we write `{prefix} {my query}`, for example `map Warsaw`.  In most cases however it would be preferable to write `{my query} {suffix}`.

     

    The advantage is that it is much easier to change the decision about the suffix than about the prefix. So if I search `map Byzantium` and Google Maps can't find it, I can change my decision, invoke Alfred again, press ↑ and change the suffix of search engine just with few keystrokes. At the moment I have to press ↑, go to the beginning of the line and then change the suffix. I can't see any disadvantages. We always know what we are looking for (query), but sometimes we are not sure what we what to look it with. Does the contrary ever happen? 

     

    The added value of this solution is that in some workflows with dynamic searches we wouldn't have to add "." at the end of the query to perform the query (which is required now to prevent premature launching of a dynamic search).

×
×
  • Create New...