Permalink
Commits on Jul 16, 2018
  1. Merge pull request #3329 from lasers/next

    Airblader committed Jul 16, 2018
    docs/i3bar-protocol: fix typo
Commits on Jul 12, 2018
  1. Merge pull request #3254 from orestisf1993/issue-555

    Airblader committed Jul 12, 2018
    Multiple assignments of workspaces to outputs (#555)
  2. Allow multiple assignments of workspaces to outputs

    orestisf1993 committed Mar 27, 2018
    Also makes get_assigned_output work with the primary output:
        workspace X output primary
    will now work.
    
    Fixes #555.
  3. Merge pull request #3327 from orestisf1993/rename-mouse-bug

    Airblader committed Jul 12, 2018
    cmd_rename_workspace: always call con_focus
  4. Merge pull request #3328 from orestisf1993/next

    Airblader committed Jul 12, 2018
    Fix ISSUE_TEMPLATE typo
  5. cmd_rename_workspace: always call con_focus

    orestisf1993 committed Jul 11, 2018
    This was introduced in 252db3b (#3245). That commit moved the
    con_activate line inside the loop, meaning it wouldn't always be called.
    
    When the mouse moved after a rename with focus_follows_mouse enabled,
    check_crossing_screen_boundary (src/handlers.c:111) called
    con_descend_focused that used the wrong focus order.
    
    I also change con_activate to con_focus since we don't really want to
    raise floating containers there.
    
    Fixes #3325
Commits on Jul 10, 2018
  1. Merge pull request #3324 from orestisf1993/xdg_config

    Airblader committed Jul 10, 2018
    Correct XDG paths precedence for config files
Commits on Jun 27, 2018
  1. Use get_assigned_output for numbers

    orestisf1993 committed Mar 28, 2018
    This prohibits the usage of workspaces assigned to other outputs in
    create_workspace_on_output.
    
    Eg, with config:
        workspace 1 output fake-0
        workspace 2 output fake-0
    and 2 screens workspace 2 would be used for the second screen even
    though it is assigned to the first one.
    
    Also introduces a test for workspace assignments that includes the case
    described above and some tests that don't fail in the next branch.
  2. Introduce get_assigned_output

    orestisf1993 committed Mar 28, 2018
    This also replaces code in create_workspace_on_output() that is
    theoretically more efficient but:
    1. It isn't a huge difference since it depends on the number of outputs,
    that shouldn't be high.
    2. get_assigned_output will be modified and used for #555, then its
    logic should be followed in create_workspace_on_output() too.
    
    Another note for create_workspace_on_output: if assigned is not NULL the
    condition (assigned != output->con) should never be false, ie if there
    is an assigned output to this name, it isn't the current one. This
    happens because the current callers check for assignments before calling
    create_workspace_on_output().
Commits on Jun 22, 2018
  1. Merge pull request #3179 from orestisf1993/issue-2733

    Airblader committed Jun 22, 2018
    Correctly handle bindings for the same key with and without --release
  2. Merge pull request #3313 from czak/fix-border-artifacts

    Airblader committed Jun 22, 2018
    Border artifacts when moving window
Commits on Jun 20, 2018
  1. Merge pull request #3309 from orestisf1993/detectable-autorepeat

    Airblader committed Jun 20, 2018
    Enable detectable autorepeat
Commits on Jun 15, 2018
  1. Merge pull request #3310 from KJoke70/patch-1

    Airblader committed Jun 15, 2018
    Update i3-msg.man: added get_config and send_tick
  2. Update i3-msg.man: added get_config and send_tick

    KJoke70 committed Jun 15, 2018
    Added get_config and send_tick which are mentioned [here](https://i3wm.org/docs/ipc.html).
  3. Enable detectable autorepeat

    orestisf1993 committed Jun 12, 2018
    https://www.x.org/releases/current/doc/kbproto/xkbproto.html#Detectable_Autorepeat
    
    Detectable autorepeat should only affect --release bindings. Currently,
    when a user keeps a key pressed, we get multiple KeyPress and KeyRelease
    events. With this change, we still get multiple KeyPress events, which
    means that you can still keep a key pressed to repeatedly execute a
    normal binding, but only one KeyRelease event when the key is physically
    released.
    
    Unfortunately, this change is not currently testable because detectable
    autorepeat doesn't seem to work under Xephyr. AwesomeWM experienced the
    same problem:
    awesomeWM/awesome@6f2424e
    
    Fixes #3306
Commits on Jun 7, 2018
  1. Merge pull request #3307 from orestisf1993/link

    Airblader committed Jun 7, 2018
    Fix link
Commits on Jun 2, 2018
  1. Merge pull request #3303 from orestisf1993/back_and_forth

    Airblader committed Jun 2, 2018
    docs: link workspace_auto_back_and_forth from workspace command
  2. docs: link workspace_auto_back_and_forth from workspace command

    orestisf1993 committed Jun 2, 2018
    The current text is confusing. '--no-auto-back-and-forth' doesn't
    disable the 'workspace back_and_forth' command, the flag is not even
    valid for that command.
  3. Merge pull request #3301 from Streetwalrus/swallow-reframe

    Airblader committed Jun 2, 2018
    Reframe swallowed windows if depth doesn't match
  4. Reframe swallowed windows if depth doesn't match

    Streetwalrus committed Jun 1, 2018
    X will not allow a window with ParentRelative background to be created
    or reparented under a window with mismatching color depth.
    Deal with this by destroying the container frame and creating a new one
    with the right depth upon swallowing.
    Defer destruction of the frame window until after the updated tree has
    been rendered to avoid some distracting flickering.
    
    Fixes #3297
Commits on May 20, 2018
  1. Updated ISSUE_TEMPLATE.md (#3295)

    Airblader authored and stapelberg committed May 20, 2018
Commits on May 9, 2018
  1. Merge pull request #3282 from orestisf1993/strncpy-to-memcpy

    Airblader committed May 9, 2018
    Replace strncpy call with memcpy when result is not NUL-terminated
Commits on May 8, 2018
  1. Replace strncpy call with memcpy when result is not NUL-terminated

    orestisf1993 committed May 8, 2018
    This fixes a new warning from GCC 8.1, -Wstringop-truncation:
    https://gcc.gnu.org/gcc-8/changes.html
    https://gcc.gnu.org/onlinedocs/gcc-8.1.0/gcc/Warning-Options.html#index-Wstringop-truncation
    
    Replacing with memcpy is what gcc suggests:
    > As another example, the following call to strncpy results in copying
    > to d just the characters preceding the terminating NUL, without
    > appending the NUL to the end. Assuming the result of strncpy is
    > necessarily a NUL-terminated string is a common mistake, and so the
    > call is diagnosed. To avoid the warning when the result is not
    > expected to be NUL-terminated, call memcpy instead.
    >    void copy (char *d, const char *s)
    >    {
    >      strncpy (d, s, strlen (s));
    >    }
Commits on May 5, 2018
  1. Merge pull request #3279 from Streetwalrus/next

    orestisf1993 committed May 5, 2018
    Activate the focused child when scrolling over tab/stack decorations
  2. Activate the focused child when scrolling over tab/stack decorations

    Streetwalrus committed May 5, 2018
    fbce834 introduced a bug where scrolling over the decoration while
    another container is focused would not focus the tabbed/stacked
    container itself, but would instead move focus through the currently
    focused container.
Commits on May 4, 2018
  1. Merge pull request #3272 from orestisf1993/fake-outputs

    Airblader committed May 4, 2018
    Fix: ConfigureNotify can crash i3 with fake-outputs
  2. Merge pull request #3277 from orestisf1993/resize-set

    Airblader committed May 4, 2018
    Resize set improvements
Commits on May 2, 2018